Skip to content
Fencer Vulns
critical 9.1

CVE-2026-22732 in the critical feed json

Under Some Conditions Spring Security HTTP Headers Are not Written

published 2026-03-19 7 mo ago modified 2026-09-10 1 mo ago also GHSA-mf92-479x-3373 , EUVD-2026-13347

cvss
9.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 43%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.springframework.security:spring-security-web 6.5.9, 7.0.4
  • vmware spring_security 5.7.22, 5.8.24, 6.3.15, 6.4.15, 6.5.9, 7.0.4

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-22732 updated cvss 6.5

Spring Security: Spring Security: Security policy bypass and information disclosure due to unwritten HTTP headers

  • Red Hat OpenShift Developer Tools and Services jenkins, ocp-tools-4/jenkins-rhel8, ocp-tools-4/jenkins-rhel9 Red Hat build of Apache Camel - HawtIO 4 spring-security-core Red Hat build of Apache Camel for Spring Boot 4 spring-security-core Red Hat build of Quarkus quarkus-spring-security-core-api Red Hat Data Grid 8 spring-security-core Red Hat Fuse 7 spring-security-core, org.apache.servicemix.bundles.spring-security-core
    +6 more products
    Red Hat JBoss Enterprise Application Platform 7 spring-security-core Red Hat JBoss Enterprise Application Platform 8 spring-security-core, quarkus-spring-security-core-api Red Hat JBoss Enterprise Application Platform Expansion Pack spring-security-core, quarkus-spring-security-core-api Red Hat OpenShift Dev Spaces devspaces/openvsx-rhel9, devspaces/pluginregistry-rhel9 Red Hat Process Automation 7 spring-security-core Red Hat Single Sign-On 7 spring-security-core
    affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
7 mo ago

Exploit prediction

0.50% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • spring.io https://spring.io/security/cve-2026-22732 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
GitHub 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
maven org.springframework.security:spring-security-web
<=5.7.14
>=5.8.0, <=5.8.16
>=6.0.0, <=6.3.10
>=6.4.0, <=6.4.13
>=6.5.0, <6.5.9
>=7.0.0, <7.0.4
6.5.9
7.0.4

Affected products

  • VMware Spring Security

Classification

Weakness
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.