Widely used Spring Security header handling bug; could disrupt many web apps.
CVE-2026-22732
Spring Security may omit configured HTTP response headers for servlet apps.
Is CVE-2026-22732 being exploited?
Not confirmed. CVE-2026-22732 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.48% probability of exploitation in the next 30 days.
How severe is CVE-2026-22732?
CVE-2026-22732 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-22732?
Yes. A fix has been recorded for CVE-2026-22732. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-22732 affect?
CVE-2026-22732 affects Spring Security 5.7.0-5.7.21, 5.8.0-5.8.23, 6.3.0-6.3.14, 6.4.0-6.4.14, and 2 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-22732?
Upgrade to a fixed Spring Security version; verify headers after upgrade.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Headers may not be written, weakening security headers (CSP, HSTS, X-Frame-Options).
Patch when possible
- affected>= 5.7.0 and <= 5.7.21
- affected>= 5.8.0 and <= 5.8.23
- affected>= 6.3.0 and <= 6.3.14
- affected>= 6.4.0 and <= 6.4.14
- affected>= 6.5.0 and <= 6.5.8
- affected>= 7.0.0 and <= 7.0.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.