How severe is GHSA-mf92-479x-3373?

GHSA-mf92-479x-3373 has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-mf92-479x-3373?

GHSA-mf92-479x-3373 affects the following packages: 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), org.springframework.security:spring-security-web (Maven), org.springframework.security:spring-security-web (Maven). Ecosystems affected: Maven.

How do I fix GHSA-mf92-479x-3373?

No patched version of org.springframework.security:spring-security-web has shipped for GHSA-mf92-479x-3373 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-mf92-479x-3373 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.security:spring-security-web. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-mf92-479x-3373 if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-mf92-479x-3373?

O3 pinpoints whether GHSA-mf92-479x-3373 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-mf92-479x-3373 actively exploited in the wild?

No public exploit code has been indexed for GHSA-mf92-479x-3373 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-mf92-479x-3373?

GHSA-mf92-479x-3373 is classified as CWE-425 (CWE-425). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-mf92-479x-3373 published, and has it been updated?

GHSA-mf92-479x-3373 was published on March 20, 2026 and was last updated on March 25, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

CRITICAL severity

GHSA-mf92-479x-3373

CRITICAL

GHSA-mf92-479x-3373 is a critical-severity (CVSS 9.1) CWE-425 vulnerability in org.springframework.security:spring-security-web. O3 Security confirms whether GHSA-mf92-479x-3373 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Spring Security HTTP Headers Are not Written Under Some Conditions

Also known asCVE-2026-22732

Published

Mar 20, 2026

Updated

Mar 25, 2026

Affected

6 pkgs

Patched

2 / 6

Exploits

None indexed

Exploitation data as of Mar 25, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

6 pkgs affected

☕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-web

Real-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: 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

6 total 2 fixed

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.9
☕Maven	`org.springframework.security:spring-security-web`	≥ 7.0.0&&< 7.0.4	7.0.4

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.security:spring-security-web. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
No patched version of org.springframework.security:spring-security-web has shipped for GHSA-mf92-479x-3373 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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.
How O3 protects you
O3 pinpoints whether GHSA-mf92-479x-3373 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-mf92-479x-3373. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-mf92-479x-3373 in your dependencies?

O3 detects GHSA-mf92-479x-3373 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works