Quick answers
- Is CVE-2026-47892 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47892 being exploited in the wild.
- How severe is CVE-2026-47892?
- Critical severity, with a CVSS score of 9.8, published 27 August 2026.
- Which products and versions are affected?
- org.springframework:spring-webflux (Maven) ECOSYSTEM:introduced=5.2.5.RELEASE,last_affected=5.2.25.RELEASE.
- Is there a fix for CVE-2026-47892?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-47892 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-47892?
- Check whether you run org.springframework:spring-webflux (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a header predicate bypass in Spring Framework's WebFlux functional endpoints when deployed with DispatcherServlet. The root cause involves improper validation of HTTP headers during pre-flight request processing, allowing attackers to craft requests that bypass header-based security predicates intended to restrict access. The attack vector is network-based and requires no authentication. An attacker can exploit this by sending specially crafted pre-flight requests to access protected endpoints or resources that should be restricted by header validation rules. Patches are available for affected versions (Spring Framework 5.2.26+, 5.3.50+, 6.0.31+, 6.1.29+, 6.2.20+, and 7.0.9+).
Affected products
- Spring Spring Framework 5.2.5.RELEASE through 5.2.25.RELEASE, 5.3.0 through 5.3.49, 6.0.0 through 6.0.30, 6.1.0 through 6.1.28, 6.2.0 through 6.2.19, 7.0.0 through 7.0.8
Identifiers
- CVE-2026-47892
- GHSA-9qf2-26p9-2q2q
Timeline
- 2026-08-27: disclosed: CVE-2026-47892 published