Threats / VMware / CVE-2022-22965
CVE-2022-22965
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
VMware Spring Framework vulnerability
Spring Framework data binding vulnerability in MVC/WebFlux on JDK 9+ allows remote code execution through unsafe object property manipulation during request processing.
Verdict
Today item — known-exploited.
A critical remote code execution flaw in Spring Framework's data binding mechanism enables unauthenticated attackers to execute arbitrary code on vulnerable servers running Java 9 or later, with active exploitation observed in the wild.
CISA KEV Yes · 2022-04-045EPSS 0.99677 (verify live)6Exploit Weaponized · public PoC7CVSS 9.8 (CISA)4CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
807 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-04-04).
Probability (EPSS)
EPSS 0.99677 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: VMware, Spring Framework. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-94 Code Injection — weakness family: Injection.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 3 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module, nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious HTTP request with specially formatted parameters targeting the data binding layer to inject code execution payloads.
Business
Attackers gain immediate code execution capability on production application servers without authentication, enabling full system compromise.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the vulnerability to establish persistent access and lateral movement within the compromised infrastructure.
Business
Breach scope expands across connected systems and data repositories, multiplying incident response costs and regulatory exposure.
3
Lateral reach — past segmentation narrative 3
Attacker
I exfiltrate sensitive data or deploy additional malware payloads for long-term control.
Business
Data theft, intellectual property loss, and operational disruption create cascading financial and reputational damage.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05