CVE-2018-1275 is a critical-severity (CVSS 9.8) Code Injection vulnerability in org.springframework:spring-messaging. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.springframework:spring-messaging — see the affected versions and patch details below.
Spring Framework has Improperly Implemented Security Check for Standard
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.springframework:spring-messaging☕org.springframework:spring-messagingReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.16 and older unsupported versions, allow applications to expose STOMP over WebSocket endpoints with a simple, in-memory STOMP broker through the spring-messaging module. A malicious user (or attacker) can craft a message to the broker that can lead to a remote code execution attack. This CVE addresses the partial fix for CVE-2018-1270 in the 4.3.x branch of the Spring Framework.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework:spring-messaging | all versions | 4.3.16.RELEASEorg.springframework:spring-messaging:4.3.16.RELEASE |
| ☕Maven | org.springframework:spring-messaging | ≥ 5.0.0.RELEASE&&< 5.0.5.RELEASE | 5.0.5.RELEASEorg.springframework:spring-messaging:5.0.5.RELEASE |
Affected Products
application testing suiteoraclebig data discoveryoraclecommunications converged application serveroraclecommunications diameter signaling routeroraclecommunications performance intelligence centeroraclecommunications services gatekeeperoracleResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework:spring-messaging, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework:spring-messaging to 4.3.16.RELEASE or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-1275 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Frequently Asked Questions
Is CVE-2018-1275 in your dependencies?
Find it across Maven, including transitive dependencies.