CVE-2026-22732 — spring-security-web
CRITICALCVE-2026-22732 is a critical-severity (CVSS 9.1) CWE-425 vulnerability in org.springframework.security:spring-security-web. A fix is available for org.springframework.security:spring-security-web — see the affected versions and patch details below.
Under Some Conditions Spring Security HTTP Headers Are not Written
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-22732.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.springframework.security:spring-security-web☕org.springframework.security:spring-security-web☕org.springframework.security:spring-security-web☕org.springframework.security:spring-security-web☕org.springframework.security:spring-security-web☕org.springframework.security:spring-security-webReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.security:spring-security-web | all versions | No fix |
| ☕Maven | org.springframework.security:spring-security-web | ≥ 5.8.0 | No fix |
| ☕Maven | org.springframework.security:spring-security-web | ≥ 6.0.0 | No fix |
| ☕Maven | org.springframework.security:spring-security-web | ≥ 6.4.0 | No fix |
| ☕Maven | org.springframework.security:spring-security-web | ≥ 6.5.0&&< 6.5.9 | 6.5.9org.springframework.security:spring-security-web:6.5.9 |
| ☕Maven | org.springframework.security:spring-security-web | ≥ 7.0.0&&< 7.0.4 | 7.0.4org.springframework.security:spring-security-web:7.0.4 |
Affected Products
spring securityvmwareDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.security:spring-security-web, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
A fix is available for CVE-2026-22732; check the affected-versions list above or the advisory for the patched release of org.springframework.security:spring-security-web, then make sure no transitive dependency still pins the vulnerable range.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.Source: Red Hat security advisory for CVE-2026-22732 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2026-22732 in your dependencies?
Find it across Maven, including transitive dependencies.