CVE-2018-1270

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 77% (99th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
9.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 77%
CISA-KEV: Not listedEPSS PROB: 77%CVSS: 9.8Exploit: Elevated riskExposed services: Not assessed

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.8CRITICALmedium confidence
EG Risk
90
EG Risk 90/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation77% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
77%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

April 6, 2018

Last Modified

October 8, 2026

Advisory Details (8)

Auto-updated Oct 8, 2026
Patch available. Sources: redhat.
genericMentions a patch (unverified)

[SECURITY] [DLA 2635-1] libspring-java security update

https://lists.debian.org/debian-lts-announce/2021/04/msg00022.html
generic

Pony Mail

https://lists.apache.org/thread.html/rf1bbc0ea4a9f014cf94df9a12a6477d24a27f52741dbc87f2fd52ff2%40%3Cissues.geode.apache.org%3E
generic

Pony Mail

https://lists.apache.org/thread.html/dcf8599b80e43a6b60482607adb76c64672772dc2d9209ae2170f369%40%3Cissues.activemq.apache.org%3E
generic

Pony Mail

https://lists.apache.org/thread.html/ab825fcade0b49becfa30235b3d54f4a51bb74ea96b6c9adb5d1378c%40%3Cissues.activemq.apache.org%3E
generic

Pony Mail

https://lists.apache.org/thread.html/6d3d34adcf3dfc48e36342aa1f18ce3c20bb8e4c458a97508d5bfed1%40%3Cissues.activemq.apache.org%3E
generic

Pony Mail

https://lists.apache.org/thread.html/4ed49b103f64a0cecb38064f26cbf1389afc12124653da2d35166dbe%40%3Cissues.activemq.apache.org%3E
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2018:2939
generic

CVE-2018-1270 - PSIRT.COM

http://www.securityfocus.com/bid/103696

Patch Availability(1)

Vendor / EcosystemFix (by version range) / 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

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
libspring-java—
  • every version up to 4.3.19-1: fixed in 4.3.19-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libspring-java—
  • every version up to 4.3.19-1: fixed in 4.3.19-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libspring-java—
  • every version up to 4.3.19-1: fixed in 4.3.19-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libspring-java—
  • every version up to 4.3.19-1: fixed in 4.3.19-1
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
libspring-java4.3.5-1
  • every version up to 4.3.5-1+deb9u1: fixed in 4.3.5-1+deb9u1
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.springframework:spring-messaging4.0.0.RELEASE ... 4.3.9.RELEASE (46 versions)
  • 5.0.0.RELEASE up to 5.0.5.RELEASE: fixed in 5.0.5.RELEASE
  • every version up to 4.3.16.RELEASE: fixed in 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 6× in last 7d / 22× 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-10-09 20:02 UTCEPSS rescore
  2. 2026-10-08 22:31 UTCVendor advisory
  3. 2026-10-08 21:35 UTCEG score recompute
  4. 2026-10-08 21:35 UTCVendor advisory
  5. 2026-10-07 23:42 UTCEPSS rescore
  6. 2026-10-06 15:12 UTCEPSS rescore
  7. 2026-10-01 19:44 UTCEPSS rescore
  8. 2026-09-30 14:59 UTCEPSS rescore
  9. 2026-09-30 09:53 UTCEG score recompute
  10. 2026-09-29 07:01 UTCOSV refresh
  11. 2026-09-28 13:45 UTCEPSS rescore
  12. 2026-09-27 13:40 UTCEPSS rescore
  13. 2026-09-26 15:53 UTCEPSS rescore
  14. 2026-09-24 13:59 UTCEPSS rescore
  15. 2026-09-24 13:59 UTCEPSS rescore
  16. 2026-09-20 20:10 UTCEPSS rescore
  17. 2026-09-18 19:22 UTCEPSS rescore
  18. 2026-09-17 19:22 UTCEPSS rescore
  19. 2026-09-16 05:06 UTCEPSS rescore
  20. 2026-09-13 16:42 UTCEPSS rescore
  21. 2026-09-12 14:56 UTCEPSS rescore
  22. 2026-09-11 09:32 UTCEPSS rescore
  23. 2026-09-09 12:53 UTCOSV refresh
  24. 2026-09-07 15:57 UTCEPSS rescore
  25. 2026-09-06 13:43 UTCEPSS rescore
Show 70 more
  1. 2026-09-05 15:24 UTCEPSS rescore
  2. 2026-09-04 05:02 UTCEPSS rescore
  3. 2026-09-01 13:49 UTCEPSS rescore
  4. 2026-08-28 21:36 UTCEPSS rescore
  5. 2026-08-26 14:42 UTCEPSS rescore
  6. 2026-08-25 13:44 UTCEPSS rescore
  7. 2026-08-22 19:37 UTCOSV refresh
  8. 2026-08-21 23:45 UTCEPSS rescore
  9. 2026-08-20 22:51 UTCEPSS rescore
  10. 2026-08-19 17:00 UTCEPSS rescore
  11. 2026-08-16 02:10 UTCEPSS rescore
  12. 2026-08-15 01:26 UTCEPSS rescore
  13. 2026-08-12 13:46 UTCEPSS rescore
  14. 2026-08-07 16:23 UTCEPSS rescore
  15. 2026-08-06 23:34 UTCOSV refresh
  16. 2026-08-05 19:13 UTCEPSS rescore
  17. 2026-08-02 02:23 UTCEPSS rescore
  18. 2026-07-30 16:24 UTCEPSS rescore
  19. 2026-07-30 01:27 UTCEPSS rescore
  20. 2026-07-26 14:51 UTCEPSS rescore
  21. 2026-07-26 14:51 UTCEPSS rescore
  22. 2026-07-25 14:14 UTCEPSS rescore
  23. 2026-07-24 14:14 UTCEPSS rescore
  24. 2026-07-24 14:14 UTCEPSS rescore
  25. 2026-07-23 01:33 UTCEG score recompute
  26. 2026-07-22 22:13 UTCEG score recompute
  27. 2026-07-22 14:05 UTCEPSS rescore
  28. 2026-07-21 15:22 UTCEPSS rescore
  29. 2026-07-21 15:17 UTCOSV refresh
  30. 2026-07-20 17:04 UTCEPSS rescore
  31. 2026-07-20 17:04 UTCEPSS rescore
  32. 2026-07-19 14:28 UTCEPSS rescore
  33. 2026-07-15 16:55 UTCEPSS rescore
  34. 2026-07-15 16:55 UTCEPSS rescore
  35. 2026-07-12 05:43 UTCEPSS rescore
  36. 2026-07-11 08:24 UTCEPSS rescore
  37. 2026-07-09 19:06 UTCEPSS rescore
  38. 2026-07-06 16:24 UTCEPSS rescore
  39. 2026-07-06 16:24 UTCEPSS rescore
  40. 2026-07-04 10:26 UTCOSV refresh
  41. 2026-07-04 06:28 UTCEPSS rescore
  42. 2026-07-04 06:28 UTCEPSS rescore
  43. 2026-07-01 15:03 UTCEPSS rescore
  44. 2026-07-01 15:03 UTCEPSS rescore
  45. 2026-06-28 04:53 UTCEPSS rescore
  46. 2026-06-28 04:53 UTCEPSS rescore
  47. 2026-06-25 13:47 UTCEPSS rescore
  48. 2026-06-25 13:47 UTCEPSS rescore
  49. 2026-06-23 21:30 UTCEPSS rescore
  50. 2026-06-23 21:30 UTCEPSS rescore
  51. 2026-06-23 21:30 UTCEPSS rescore
  52. 2026-06-21 01:57 UTCEPSS rescore
  53. 2026-06-21 01:57 UTCEPSS rescore
  54. 2026-06-17 17:50 UTCEPSS rescore
  55. 2026-06-17 17:50 UTCEPSS rescore
  56. 2026-06-15 22:14 UTCOSV refresh
  57. 2026-06-15 17:45 UTCEPSS rescore
  58. 2026-06-14 23:15 UTCEPSS rescore
  59. 2026-06-14 23:14 UTCEPSS rescore
  60. 2026-06-13 22:58 UTCEPSS rescore
  61. 2026-06-10 22:16 UTCEPSS rescore
  62. 2026-06-04 13:10 UTCEPSS rescore
  63. 2026-06-01 13:50 UTCEPSS rescore
  64. 2026-06-01 13:50 UTCEPSS rescore
  65. 2026-05-29 13:41 UTCEPSS rescore
  66. 2026-05-28 09:31 UTCEG score recompute
  67. 2026-05-28 09:31 UTCVendor advisory
  68. 2026-05-27 13:38 UTCEPSS rescore
  69. 2026-05-27 13:38 UTCEPSS rescore
  70. 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 ↗

Related CVEs(same product + same vendor + same CWE)

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 on April 6, 2018, with the most recent update on October 8, 2026. 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 77% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
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?
A fix for CVE-2018-1270 is available: update to the fixed version the vendor names in its advisory.

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.

Book a Demo →Browse All CVEs