CVE-2018-1273

CRITICALNVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-03-25), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Exploited in the wild
9.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 96%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Spring Data Commons, versions prior to 1.13 to 1.13.10, 2.0 to 2.0.5, and older unsupported versions, contain a property binder vulnerability caused by improper neutralization of special elements. An unauthenticated remote malicious user (or attacker) can supply specially crafted request parameters against Spring Data REST backed HTTP resources or using Spring Data's projection-based request payload binding hat can lead to a remote code execution attack.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
—
EPSS
99.9%
KEV
⚠ Exploited

Published

April 11, 2018

Last Modified

June 26, 2026

Advisory Details (2)

Auto-updated Jul 12, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: cisa.
cisa Patch Available🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2018-1273
generic
http://mail-archives.apache.org/mod_mbox/ignite-dev/201807.mbox/%3CCAK0qHnqzfzmCDFFi6c5Jok19zNkVCz5Xb4sU%3D0f2J_1i4p46zQ%40mail.gmail.com%3E

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.springframework.data:spring-data-commons2.0.0.RELEASE ... 2.0.5.RELEASE (6 versions)2.0.6—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 19× 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-22 21:47 UTCEG score recompute
  2. 2026-07-22 19:40 UTCCISA KEV update
  3. 2026-07-21 14:37 UTCCISA KEV update
  4. 2026-07-17 07:32 UTCEG score recompute
  5. 2026-07-16 17:04 UTCCISA KEV update
  6. 2026-07-15 16:49 UTCCISA KEV update
  7. 2026-07-15 15:04 UTCCISA KEV update
  8. 2026-07-14 18:05 UTCCISA KEV update
  9. 2026-07-13 17:07 UTCCISA KEV update
  10. 2026-07-11 08:24 UTCEPSS rescore
  11. 2026-07-10 17:52 UTCCISA KEV update
  12. 2026-07-09 19:06 UTCEPSS rescore
  13. 2026-07-08 15:11 UTCEPSS rescore
  14. 2026-07-07 19:01 UTCCISA KEV update
  15. 2026-07-07 17:16 UTCCISA KEV update
  16. 2026-07-01 19:16 UTCCISA KEV update
  17. 2026-06-29 19:12 UTCCISA KEV update
  18. 2026-06-25 19:15 UTCCISA KEV update
  19. 2026-06-23 17:44 UTCCISA KEV update
  20. 2026-06-22 14:23 UTCEPSS rescore
  21. 2026-06-21 01:57 UTCEPSS rescore
  22. 2026-06-21 01:57 UTCEPSS rescore
  23. 2026-06-18 16:13 UTCCISA KEV update
  24. 2026-06-16 19:33 UTCCISA KEV update
  25. 2026-06-15 19:33 UTCCISA KEV update
Show 21 more
  1. 2026-06-15 17:45 UTCEPSS rescore
  2. 2026-06-12 17:35 UTCCISA KEV update
  3. 2026-06-11 19:10 UTCCISA KEV update
  4. 2026-06-10 22:16 UTCEPSS rescore
  5. 2026-06-09 18:42 UTCCISA KEV update
  6. 2026-06-09 17:12 UTCCISA KEV update
  7. 2026-06-08 19:16 UTCCISA KEV update
  8. 2026-06-08 17:26 UTCCISA KEV update
  9. 2026-06-05 22:43 UTCCISA KEV update
  10. 2026-06-03 19:09 UTCCISA KEV update
  11. 2026-06-02 18:32 UTCCISA KEV update
  12. 2026-06-01 20:42 UTCCISA KEV update
  13. 2026-05-31 22:29 UTCEPSS rescore
  14. 2026-05-29 22:20 UTCCISA KEV update
  15. 2026-05-27 20:35 UTCCISA KEV update
  16. 2026-05-27 13:38 UTCEPSS rescore
  17. 2026-05-27 13:38 UTCEPSS rescore
  18. 2026-05-26 19:25 UTCEG score recompute
  19. 2026-05-26 19:13 UTCCISA KEV update
  20. 2026-05-26 07:17 UTCEPSS rescore
  21. 2026-05-26 07:17 UTCEPSS rescore

Publicly available exploits

(5 references)

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

  • GitHub PoCjas502n/cve-2018-1273
    First seen Apr 29, 2019

    Spring Data Commons RCE 远程命令执行漏洞

    Open source ↗
  • GitHub PoCwebr0ck/poc-cve-2018-1273
    First seen Oct 5, 2018
    Open source ↗
  • GitHub PoCwearearima/poc-cve-2018-1273
    First seen Apr 17, 2018

    POC for CVE-2018-1273

    Open source ↗
  • GitHub PoCknqyf263/CVE-2018-1273
    First seen Apr 13, 2018

    Environment for CVE-2018-1273 (Spring Data Commons)

    Open source ↗
  • Nucleihttp/cves/2018/CVE-2018-1273.yaml
    First seen Jan 1, 2018

    Spring Data Commons - Remote Code Execution

    Open source ↗

Related CVEs(same CWE)

Frequently asked(6)

What is CVE-2018-1273?
CVE-2018-1273 is a critical vulnerability published on April 11, 2018. Spring Data Commons, versions prior to 1.13 to 1.13.10, 2.0 to 2.0.5, and older unsupported versions, contain a property binder vulnerability caused by improper neutralization of special elements. An unauthenticated remote malicious user (or attacker) can supply specially crafted request parameters…
When was CVE-2018-1273 disclosed?
CVE-2018-1273 was first published in the National Vulnerability Database on April 11, 2018, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-1273 actively exploited?
Yes. CISA added CVE-2018-1273 to the Known Exploited Vulnerabilities catalog on March 25, 2022, affecting VMware Tanzu Spring Data Commons. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2018-1273?
CVE-2018-1273 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2018-1273?
CVE-2018-1273 affects VMware Tanzu Spring Data Commons. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2018-1273?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-1273, 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-1273

Explore →

Is Your Infrastructure Affected by CVE-2018-1273?

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

Start Free Scan →Browse All CVEs