CVE-2018-1270

CRITICALNVD 9.89.8
EchelonGraph scoreHIGH confidence

Score elevated to 9.8 because EPSS predicts 90% probability of exploitation within the next 30 days (top 0.4% of all CVEs). NVD baseline CVSS 9.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Elevated
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 77%
CISA-KEV: Not listedEPSS: 77%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.15 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.

CVSS v3
9.8
EG Score
9.8(high)
EPSS
99.5%
KEV
Not listed

Published

April 6, 2018

Last Modified

November 21, 2024

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpatch2018-10-17redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.springframework:spring-messaging4.0.0.RELEASE ... 4.3.9.RELEASE (46 versions)4.3.16.RELEASE

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 4× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:24 UTCEPSS rescore
  2. 2026-07-09 19:06 UTCEPSS rescore
  3. 2026-07-06 16:24 UTCEPSS rescore
  4. 2026-07-06 16:24 UTCEPSS rescore
  5. 2026-07-04 10:26 UTCOSV refresh
  6. 2026-07-04 06:28 UTCEPSS rescore
  7. 2026-07-04 06:28 UTCEPSS rescore
  8. 2026-07-01 15:03 UTCEPSS rescore
  9. 2026-07-01 15:03 UTCEPSS rescore
  10. 2026-06-28 04:53 UTCEPSS rescore
  11. 2026-06-28 04:53 UTCEPSS rescore
  12. 2026-06-25 13:47 UTCEPSS rescore
  13. 2026-06-25 13:47 UTCEPSS rescore
  14. 2026-06-23 21:30 UTCEPSS rescore
  15. 2026-06-23 21:30 UTCEPSS rescore
  16. 2026-06-23 21:30 UTCEPSS rescore
  17. 2026-06-21 01:57 UTCEPSS rescore
  18. 2026-06-21 01:57 UTCEPSS rescore
  19. 2026-06-17 17:50 UTCEPSS rescore
  20. 2026-06-17 17:50 UTCEPSS rescore
  21. 2026-06-15 22:14 UTCOSV refresh
  22. 2026-06-15 17:45 UTCEPSS rescore
  23. 2026-06-14 23:15 UTCEPSS rescore
  24. 2026-06-14 23:14 UTCEPSS rescore
  25. 2026-06-13 22:58 UTCEPSS rescore
Show 10 more
  1. 2026-06-10 22:16 UTCEPSS rescore
  2. 2026-06-04 13:10 UTCEPSS rescore
  3. 2026-06-01 13:50 UTCEPSS rescore
  4. 2026-06-01 13:50 UTCEPSS rescore
  5. 2026-05-29 13:41 UTCEPSS rescore
  6. 2026-05-28 09:31 UTCEG score recompute
  7. 2026-05-28 09:31 UTCVendor advisory
  8. 2026-05-27 13:38 UTCEPSS rescore
  9. 2026-05-27 13:38 UTCEPSS rescore
  10. 2026-05-24 21:42 UTCOSV refresh

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCCaledoniaProject/CVE-2018-1270
    First seen Apr 7, 2018

    Spring messaging STOMP protocol RCE

    Open source ↗

Frequently asked(5)

What is CVE-2018-1270?
CVE-2018-1270 is a critical vulnerability published on April 6, 2018. Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.15 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…
When was CVE-2018-1270 disclosed?
CVE-2018-1270 was first published in the National Vulnerability Database on April 6, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-1270 actively exploited?
CVE-2018-1270 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-1270?
CVE-2018-1270 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2018-1270?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-1270, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-1270

Explore →

Is Your Infrastructure Affected by CVE-2018-1270?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.