basicsecurity.net
Proof, not just disclosure.
Threats / VMware / CVE-2022-22965
CVE-2022-22965 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

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-043EPSS 0.99677 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit 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
764 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).
CISA KEV ↗Confirmed
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
Affected: VMware, Spring Framework. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-94 Code Injection — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-94 · Code InjectionInjection
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 764 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by vmware (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by vmwareCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.