CVE Intelligence
CISA KEV Critical Injection

CVE-2018-1273 — VMware Tanzu Spring Data Commons Property Binder Vulnerability

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.

Published Apr 11, 2018 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, NIST National Vulnerability Database, GitHub Security Advisories, CVE Program (cve.org) e CISA ADP · CNA: dell

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • Used in ransomware campaigns (CISA)+10
  • Public exploit/PoC (nuclei)+4
  • EPSS 97% (30-day exploitation probability)+15
  • Technical severity (critical)+10
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed Mar 25, 2022
EPSS FIRST
96.96%
ahead of 100% of scored CVEs · Oct 14, 2026
Affects
Apache Software Foundation
Ignite and 5 more
CVSS base
9.8
Critical · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — www.oracle.com (NIST National Vulnerability Database)
  • Maven Org.springframework.data:spring-data-commons: fixed in version 1.13.11 — github.com (GitHub Security Advisories)
  • Maven Org.springframework.data:spring-data-commons: fixed in version 2.0.6 — github.com (GitHub Security Advisories)

CISA required action CISA

Apply updates per vendor instructions.

US federal deadline: Apr 15, 2022 — passed 1644 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Apache Software Foundation Ignite, Broadcom Spring Data Commons, Oracle Financial Services Crime And Compliance Management Studio…).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  4. Apply the fixed version or the patch documented under Remediation.
  5. EPSS ahead of 100% of scored CVEs: prioritize it in the patch queue.
  6. Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Apache Software Foundation Ignite ≥ 1.0.1 and ≤ 2.5.0version 1.0.0version 1.0.0-rc3 Vulnerable NIST National Vulnerability Database
Broadcom Spring Data Commons ≤ 1.12.10≥ 1.13.0 and ≤ 1.13.10≥ 2.0.0 and ≤ 2.0.5 Vulnerable NIST National Vulnerability Database
Oracle Financial Services Crime And Compliance Management Studio version 8.0.8.2.0version 8.0.8.3.0 Vulnerable NIST National Vulnerability Database
Pivotal Software Spring Data Rest ≥ 3.0.0 and ≤ 3.0.5 Vulnerable NIST National Vulnerability Database
Spring by Pivotal Spring Framework version Versions prior to 1.13 to 1.13.10, 2.0 to 2.0.5, and older unsupported versions Vulnerable CVE Program (cve.org) e CISA ADP
Vmware Spring Data Rest ≤ 2.5.10≥ 2.6.0 and ≤ 2.6.10 Vulnerable NIST National Vulnerability Database
Maven Org.springframework.data:spring-data-commons ≥ 1.13.0 and < 1.13.11≥ 2.0.0 and < 2.0.6 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
9.8 CVSS 3.1 Critical 3.9 5.9 nvd@nist.gov via NIST National Vulnerability Database
9.8 CVSS 3.1 Critical 3.9 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
9.8 CVSS 3.1 Critical — — CISA-ADP via CVE Program (cve.org) e CISA ADP
9.8 CVSS 3.0 Critical — — GitHub, Inc. via GitHub Security Advisories
7.5 CVSS 2.0 High 10.0 6.4 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-94 · Code Injection

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
Mar 25, 2022
Federal deadline
Apr 15, 2022
passed 1644 day(s) ago
Ransomware use
Known

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

Public exploits, PoCs and detection templates

Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.

Detection templates (Nuclei)

Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 96.96%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Look for parameters with command/query metacharacters and unexpected child processes of the service.
  • Hunt retroactively in logs from before Mar 25, 2022 (KEV listing): exploitation may have started earlier.
web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · spring by pivotal/spring framework
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Fix documented
    Oct 13, 2026 · GitHub Security Advisories
  • Affected products added · maven/org.springframework.data:spring-data-commons
    Oct 13, 2026 · GitHub Security Advisories
  • Record published
    Oct 13, 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • Affected products added · broadcom/spring data commons, pivotal software/spring data rest, vmware/spring data rest, apache/ignite, oracle/financia
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 9.8
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • 2022
  • Added to CISA KEV catalog
    Mar 24, 2022 · CISA
  • 2018
  • CVE published
    Apr 11, 2018 · dell

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

9 on the record

Elsewhere on this site

Apache Software Foundation
every CVE for this vendor
2022-03
what else CISA listed that month
Injection
same class
CWE-94
other pages naming this weakness

Related CVEs (same products)

  • High CVE-2026-41728 Spring Data REST JSON Patch bypasses Jackson read-only property protection on nested objects and collections Jun 9, 2026
  • Medium CVE-2026-41837 Spring Data REST Querydsl integration exposes Jackson-hidden persistent fields as filter keys Jun 9, 2026
  • Medium CVE-2026-41730 Spring Data REST exposes persistence-layer internals in error responses Jun 9, 2026
  • High CVE-2026-41729 Spring Data REST SpEL Injection via Map Key in JSON Patch Jun 9, 2026
  • High CVE-2026-41716 Spring Data web support unbounded negative-result cache keyed on attacker-supplied property names Jun 9, 2026
  • Medium CVE-2026-41711 Potential Denial of Service through crafted Sort Parameters Jun 9, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2018-1273 is "VMware Tanzu Spring Data Commons Property Binder Vulnerability", rated Critical. It affects Ignite (Apache Software Foundation); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 9.8 describes technical severity. EPSS 96.96% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.