CVE-2026-22732: Spring Security HTTP Headers Are not Written Under Some Conditions

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
• EPSS 0.5%, percentile 41: FIRST’s model estimates a 0.5% chance of exploitation activity in the next 30 days, higher than 41% of all scored CVEs (low). EPSS is a probability, not a verdict.
• Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
• Only applies if your dependency tree includes org.springframework.security:spring-security-web (Maven) <= 5.7.14, no fixed version listed; org.springframework.security:spring-security-web (Maven) >= 5.8.0, <= 5.8.16, no fixed version listed; org.springframework.security:spring-security-web (Maven) >= 6.0.0, <= 6.3.10, no fixed version listed; org.springframework.security:spring-security-web (Maven) >= 6.4.0, <= 6.4.13, no fixed version listed. Check your lockfile, including transitive dependencies.

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.

From the GitHub advisory

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: 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 type: CWE-425.

Product: org.springframework.security:spring-security-web (Maven) · Assigned by: vmware · Published: 2026-03-19

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Privileges required: none (no login)
• User interaction: none
• Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
• CISA SSVC assessment: exploitation none, automatable yes, technical impact total.
• FIRST EPSS (model of 2026-10-21): 0.49% probability of exploitation activity in the next 30 days; percentile 41.

Timeline

• 2026-03-19 — CVE record published by vmware
• 2026-03-20 — GitHub-reviewed advisory GHSA-mf92-479x-3373 published (critical)
• 2026-04-02 — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

1. GitHub Advisory GHSA-mf92-479x-3373 github.com
2. CVE.org record CVE-2026-22732 cve.org
3. NVD entry CVE-2026-22732 nvd.nist.gov

Other references from the CVE record and advisory

1. spring.io spring.io

Critical Maven advisories · Today’s Security Digest