CVE-2026-47892 — spring-webflux
CRITICALCVE-2026-47892 is a critical-severity (CVSS 9.8) CWE-863 vulnerability in org.springframework:spring-webflux. A fix is available for org.springframework:spring-webflux — see the affected versions and patch details below.
Spring Framework Header Predicate Bypass in WebFlux Functional Endpoints
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-47892.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-47892 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.springframework:spring-webflux☕org.springframework:spring-webflux☕org.springframework:spring-webflux☕org.springframework:spring-webflux☕org.springframework:spring-webflux☕org.springframework:spring-webfluxReal-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
A WebFlux application using functional endpoints and deployed with DispatcherServlet may be vulnerable to a header predicate bypass in a pre-flight request. Spring Framework 7.0.0 - 7.0.8 Spring Framework 6.2.0 - 6.2.19 Spring Framework 6.1.0 - 6.1.28 Spring Framework 6.0.0 - 6.0.30 Spring Framework 5.3.0 - 5.3.49 Spring Framework 5.2.5.RELEASE - 5.2.25.RELEASE
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework:spring-webflux | ≥ 5.2.5.RELEASE | No fix |
| ☕Maven | org.springframework:spring-webflux | ≥ 5.3.0 | No fix |
| ☕Maven | org.springframework:spring-webflux | ≥ 6.0.0 | No fix |
| ☕Maven | org.springframework:spring-webflux | ≥ 6.1.0 | No fix |
| ☕Maven | org.springframework:spring-webflux | ≥ 6.2.0 | No fix |
| ☕Maven | org.springframework:spring-webflux | ≥ 7.0.0&&< 7.0.9 | 7.0.9org.springframework:spring-webflux:7.0.9 |
Affected Products
spring frameworkvmwareDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework:spring-webflux, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
No patched version of org.springframework:spring-webflux has shipped for CVE-2026-47892 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Applications should avoid relying solely on header-based route predicates (headers(...)) in WebFlux functional endpoint configurations to enforce security-relevant access control, since this bypass allows such guards to be circumvented via a crafted CORS pre-flight request. Combining header predicates with a dedicated authentication/authorization layer (e.g., Spring Security) prevents exploitation of this specific issue. For Red Hat Fuse 7, which is in Extended Life Support Phase 2 and will not receive a fix for this issue, this configuration- based guidance is the only available mitigation.Source: Red Hat security advisory for CVE-2026-47892 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2026-47892 in your dependencies?
Find it across Maven, including transitive dependencies.