Widely-used gateway product; header spoofing may bypass trust-based access/audit controls.
CVE-2026-47825
Header spoofing in Spring Cloud Gateway via untrusted proxies.
Is CVE-2026-47825 being exploited?
Not confirmed. CVE-2026-47825 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.14% probability of exploitation in the next 30 days.
How severe is CVE-2026-47825?
CVE-2026-47825 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-47825?
Yes. A fix has been recorded for CVE-2026-47825. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-47825 affect?
CVE-2026-47825 affects Spring Cloud Gateway 3.1.x (3.1.13 fix), Spring Cloud Gateway 4.1.x (4.1.13), Spring Cloud Gateway 4.2.x (4.2.9), Spring Cloud Gateway 4.3.x (4.3.5), and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-47825?
Upgrade to fixed versions ASAP.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Spoofed client identity via X-Forwarded-For/Forwarded headers; may bypass access controls or auditing.
Patch when possible
- affected>= 3.1.0 and < 3.1.13
- affected>= 4.1.0 and < 4.1.13
- affected>= 4.2.0 and < 4.2.9
- affected>= 4.3.0 and < 4.3.4.1
- affected>= 5.0.0 and < 5.0.1.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.