Skip to main content
VulnerabilityPublished Updated

CVE-2026-22732: VMware Spring Security · CWE-425

Affects VMware Spring SecuritySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.1 Critical.

Data as of 31 Oct 2026, 20:20 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
VMwareSpring SecurityAffected
  • >=5.7.0 <=5.7.21
  • >=5.8.0 <=5.8.23
  • >=6.3.0 <=6.3.14
  • >=6.4.0 <=6.4.14
  • >=6.5.0 <=6.5.8
  • >=7.0.0 <=7.0.3
Fixed in–
Mavenorg.springframework.security/spring-security-corepkg:maven/org.springframework.security/spring-security-coreOther threatsAffected
  • 5.7.0 – 7.0.0
  • <=5.7.21
  • >=5.8.0
  • <=5.8.23
  • >=6.3.0
  • <=6.3.14
  • >=6.4.0
  • <=6.4.14
  • >=6.5.0
  • <=6.5.8
  • >=7.0.0
  • <=7.0.3
7 affected builds
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, consider reviewing application configurations related to HTTP header management and evaluate if disabling lazy header writing or applying workarounds is possible based on vendor guidance once released.

Description

When applications specify HTTP response headers for servlet applications using Spring Security, there is the possibility that the HTTP Headers will not be written.  This issue affects Spring Security Servlet applications using lazy (default) writing of HTTP Headers: : from 5.7.0 through 5.7.21, from 5.8.0 through 5.8.23, from 6.3.0 through 6.3.14, from 6.4.0 through 6.4.14, from 6.5.0 through 6.5.8, from 7.0.0 through 7.0.3.

References

Community reviews

Loading reviews…