CVE-2026-22732: CVE-2026-22732: When applications specify HTTP response headers for servlet applications using Spring Secu…
vmware · spring security · NVD published 2026-03-20 · posted 2026-04-07 · last modified 2026-06-17
What it is
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.
| Weakness | CWE-425 |
|---|---|
| CVSS vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N (source: [email protected]) |
| ATT&CK tactics | n/a |
Exploitation evidence
First exploit evidence seen: 2026-04-07 (earliest date across the sources below).
Exploited in the wild
No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).
Public exploit code
GitHub proof-of-concept repositories
3 public repositories from 3 accounts, first seen 2026-04-07. Most starred: semgrep/cve-2026-22732-demo (0 stars), view repository.
Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.
Sources: nomi-sec/PoC-in-GitHub.
How to fix it
Fixed versions
- vmware spring security: upgrade to 5.7.22 or later
- vmware spring security: upgrade to 5.8.24 or later (affected from 5.8.0)
- vmware spring security: upgrade to 6.3.15 or later (affected from 6.3.0)
- vmware spring security: upgrade to 6.4.15 or later (affected from 6.4.0)
- vmware spring security: upgrade to 6.5.9 or later (affected from 6.5.0)
- vmware spring security: upgrade to 7.0.4 or later (affected from 7.0.0)
Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.
Vendor advisories and patches
- https://spring.io/security/cve-2026-22732 (Exploit, Vendor Advisory)
Detection Generic guidance
Response checklist Generic guidance
- Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
- Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
- Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
- Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.