How severe is CVE-2018-1273?

CVE-2018-1273 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2018-1273?

CVE-2018-1273 affects the following packages: org.springframework.data:spring-data-commons (Maven), org.springframework.data:spring-data-commons (Maven). Ecosystems affected: Maven.

How do I fix CVE-2018-1273?

Update org.springframework.data:spring-data-commons to 1.13.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-1273 is resolved across your whole dependency graph.

How do I detect CVE-2018-1273 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.data:spring-data-commons, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2018-1273 if there is no patch (or I can't update yet)?

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.

Is CVE-2018-1273 actively exploited in the wild?

Yes. There are 11 known exploit references for CVE-2018-1273, including 7 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2018-1273?

CVE-2018-1273 has an EPSS (Exploit Prediction Scoring System) score of 97.0%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2018-1273 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2018-1273 (VMware Tanzu Spring Data Commons Property Binder Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-03-25. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-04-15. The required action was: Apply updates per vendor instructions. This CVE has been used in known ransomware campaigns. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2018-1273?

CVE-2018-1273 is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2018-1273?

A Nuclei detection template exists for CVE-2018-1273, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2018-1273 published, and has it been updated?

CVE-2018-1273 was published on April 11, 2018 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

CISA KEV · ACTIVELY EXPLOITED

CRITICAL severity

CVE-2018-1273 — spring-data-commons

CRITICALFix: spring-projects/spring-data-commons@ae1dd27

CVE-2018-1273 is a critical-severity (CVSS 9.8) Code Injection vulnerability in org.springframework.data:spring-data-commons. It is in CISA's Known Exploited Vulnerabilities catalog (added 2022-03-25) and has been used in ransomware campaigns — treat it as actively exploited and patch now. A fix is available for org.springframework.data:spring-data-commons — see the affected versions and patch details below.

Spring Data Commons remote code injection vulnerability

Also known asGHSA-4fq3-mr56-cg6r

Published

Apr 11, 2018

Updated

Oct 20, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

11 known

Exploitation data as of Oct 19, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2022-03-25 — including use in ransomware campaigns. Federal agencies were required to remediate by 2022-04-15.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2018-1273.

EPSS Exploitation Probability

via FIRST.org ↗

97.0%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2018-1273 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 394,415 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected

☕org.springframework.data:spring-data-commons☕org.springframework.data:spring-data-commons

Real-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 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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework.data:spring-data-commons`	≥ 1.13.0&&< 1.13.11	1.13.11`org.springframework.data:spring-data-commons:1.13.11`
☕Maven	`org.springframework.data:spring-data-commons`	≥ 2.0.0&&< 2.0.6	2.0.6`org.springframework.data:spring-data-commons:2.0.6`

Affected Products

5 products · 11 configurations

Application

igniteapache

≥ 1.0.1 && ≤ 2.5.0

1 version

1.0.0

Application

spring data commonsbroadcom

≥ 2.0.0 && ≤ 2.0.5

range

Application

financial services crime and compliance management studiooracle

2 versions

8.0.8.2.08.0.8.3.0

Application

spring data restpivotal_software

≥ 3.0.0 && ≤ 3.0.5

range

Application

spring data restvmware

≥ 2.6.0 && ≤ 2.6.10

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.