# Spring Security HTTP Headers Are not Written Under Some Conditions

Advisory record · `GHSA-mf92-479x-3373`

- **Identifiers:** `GHSA-mf92-479x-3373` · `CVE-2026-22732`
- **State:** Confirmed
- **Severity:** CVSS 9.1 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-425](https://cwe.mitre.org/data/definitions/425.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 20 Mar 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 20 Mar 2026, 00:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.1: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `org.springframework.security:spring-security-web` (Maven): affected `<=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`; fixed in `6.5.9`, `7.0.4`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Spring Security's spring-security-web package is affected in versions 5.7.0 through 5.7.21, 5.8.0 through 5.8.23, 6.3.0 through 6.3.14, 6.4.0 through 6.4.14, 6.5.0 through 6.5.8, and 7.0.0 through 7.0.3. In these versions, HTTP response headers that applications configure for servlet applications may not be written under some conditions. The source gives few details about how an attacker would trigger this or what impact it has, though it is rated critical. Upgrade spring-security-web to 6.5.9 or 7.0.4, or to a later release in your line.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.1 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`, from CNA (vmware)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0050, the 43rd percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:17 UTC: First seen by agentprime
- 31 Oct 2026, 14:17 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-mf92-479x-3373)

## Sources

- [GitHub Advisory Database: GHSA-mf92-479x-3373](https://github.com/advisories/GHSA-mf92-479x-3373)
- [OSV: GHSA-mf92-479x-3373](https://osv.dev/vulnerability/GHSA-mf92-479x-3373)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-22732>
- <https://github.com/spring-projects/spring-security>
- <https://spring.io/security/cve-2026-22732>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-mf92-479x-3373>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-mf92-479x-3373/>. Everything for agents: <https://agentprime.io/llms.txt>.