CVE-2018-1273: 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…
Noroxi assessment
Priority: Now (action score 98/100)
- CISA has confirmed exploitation in the wild (Mar 25, 2022); it is known to be used in ransomware campaigns. Remediation deadline for US federal agencies: Apr 15, 2022.
- A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
- Probability of exploitation in the next 30 days: 96.9% (FIRST EPSS); higher than 99.8% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: org.springframework.data:spring-data-commons (Maven) 1.13.11, 2.0.6.
Patch today or shut off access. Upgrade to org.springframework.data:spring-data-commons (Maven) 1.13.11, 2.0.6 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · CISA KEV · FIRST EPSS
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
- Aug 26, 2026
- EPSS
- 96.9% · 99th percentile
- CWE
- CWE-94
Report tools
Action score
98
Patch today or shut off access.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 30 / 30 · Listed
- EPSS
- 29 / 30 · 96.9%
CISA SSVC decision
- Exploitation
- active
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Actively exploited in the wild
CISA added this to its Known Exploited Vulnerabilities catalog on Mar 25, 2022. That signals real attacks, not theory.
Remediation deadline for US federal agencies: Apr 15, 2022.
Known to be used in ransomware campaigns.
Get told when this record changes
- In CISA KEV: exploitation in the wild confirmed
- Weaponized exploit exists
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| broadcom | spring data commons | cpe:2.3:a:broadcom:spring_data_commons |
| pivotal software | spring data rest | cpe:2.3:a:pivotal_software:spring_data_rest |
| vmware | spring data rest | cpe:2.3:a:vmware:spring_data_rest |
| apache | ignite | cpe:2.3:a:apache:ignite |
| oracle | financial services crime and compliance management studio | cpe:2.3:a:oracle:financial_services_crime_and_compliance_management_studio |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (dell). Independent of NVD's CPE analysis and usually ahead of it.
Spring by Pivotal Spring Framework
- Versions prior to 1.13 to 1.13.10, 2.0 to 2.0.5, and older unsupported versionsaffected
Affected versions · NVD (10)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apache ignite1.0.1 and later · up to 2.5.0 inclusive
- apache ignite1.0.0
- broadcom spring data commons1.13.0 and later · up to 1.13.10 inclusive
- broadcom spring data commons2.0.0 and later · up to 2.0.5 inclusive
- broadcom spring data commonsup to 1.12.10 inclusive
- oracle financial services crime and compliance management studio8.0.8.2.0
- oracle financial services crime and compliance management studio8.0.8.3.0
- pivotal software spring data rest3.0.0 and later · up to 3.0.5 inclusive
- vmware spring data rest2.6.0 and later · up to 2.6.10 inclusive
- vmware spring data restup to 2.5.10 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.springframework.data:spring-data-commons | from 1.13.0 · before 1.13.11 | 1.13.11 |
| Maven | org.springframework.data:spring-data-commons | from 2.0.0 · before 2.0.6 | 2.0.6 |
Same product
broadcom: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-1274Spring Data Commons, versions 1.13 to 1.13.10, 2.0 to 2.0.5, and older unsupported versions, contain a property path parser vulnerability…31Monitor
- CVE-2026-41716Spring Data web support unbounded negative-result cache keyed on attacker-supplied property names30Monitor
- CVE-2026-41695Denial of Service in Spring Data Commons Property Path Resolution30Monitor
Published before and after this one in the same product
- Later →CVE-2026-41711Jun 9, 2026 · Potential Denial of Service through crafted Sort Parameters23Monitor
- Later →CVE-2026-41721Jun 9, 2026 · Spring Data Commons Denial of Service via Data Binding23Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:org.springframework.data:spring-data-commons | 1.13.11 | Package registry (OSV) |
| Maven:org.springframework.data:spring-data-commons | 2.0.6 | Package registry (OSV) |
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Nuclei detection template ×1
- Proof-of-concept repository on GitHub ×7
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | 7 repositories | 2018-04-13 → 2026-10-08 |
| Nuclei detection template | Nuclei template CVE-2018-1273 | — |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+2 d
- CISA KEV+1444 d
- TodayNov 14, 2026+3139 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-94 · Improper Control of Generation of Code ('Code Injection')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.