Spring Security HTTP Headers Are not Written Under Some Conditions (CVE-2026-22732) | HOL Guard CVE

Critical · CVSS 9.1CVE-2026-22732GHSA-MF92-479X-3373

Spring Security HTTP Headers Are not Written Under Some Conditions

Answer in brief

CVE-2026-22732 records a Critical severity (CVSS 9.1) vulnerability in Spring Security HTTP Headers Are not Written Under Some Conditions. The current sources do not mark it as known exploited. The current feed maps org.springframework.security:spring-security-web (maven), org.springframework.security:spring-security-web (maven), org.springframework.security:spring-security-web (maven), org.springframework.security:spring-security-web (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Mar 20, 2026Updated Sep 10, 2026Source checked Sep 10, 2026First seen by HOL Aug 7, 2026Material review Sep 10, 2026

Upstream Advisory

Key facts

Risk: Critical · CVSS 9.1
Exploitation: Not marked as known exploited
Affected software: 6 mapped packages or products
Fix availability: Available

Why this deserves its current priority

CVSS is 9.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps org.springframework.security:spring-security-web (maven), org.springframework.security:spring-security-web (maven), org.springframework.security:spring-security-web (maven), org.springframework.security:spring-security-web (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
org.springframework.security:spring-security-webmaven	>=0	Not reported
org.springframework.security:spring-security-webmaven	>=5.8.0	Not reported
org.springframework.security:spring-security-webmaven	>=6.0.0	Not reported
org.springframework.security:spring-security-webmaven	>=6.4.0	Not reported
org.springframework.security:spring-security-webmaven	>=6.5.0 <6.5.9	6.5.9
org.springframework.security:spring-security-webmaven	>=7.0.0 <7.0.4	7.0.4

Recommended response

Check inventory. Check lockfiles and deployed manifests for org.springframework.security:spring-security-web, org.springframework.security:spring-security-web, org.springframework.security:spring-security-web.
Review the reported fix. Update org.springframework.security:spring-security-web to 6.5.9; org.springframework.security:spring-security-web to 7.0.4 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Mar 20, 2026
Evidence: source:osv:source_dates:source-dates:record
Source modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:record
First seen by HOL
Aug 7, 2026

Sources and claim methodology

Upstream source 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: 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.

Quoted source text, attributed separately from HOL analysis.