# CVE-2026-47892: Spring Framework Header Predicate Bypass in WebFlux Functional Endpoints > Attackers can bypass header predicates in Spring WebFlux functional endpoints during pre-flight requests, potentially circumventing security controls. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 27 Aug 2026 - **Updated:** 28 Aug 2026 - **Also known as:** CLEANSTART-2026-CI58129, CLEANSTART-2026-LT41646, CLEANSTART-2026-WK76356, CLEANSTART-2026-YE65839, DEBIAN-CVE-2026-47892, ECHO-145e-f4d1-a3a6, GHSA-9qf2-26p9-2q2q, ROOT-APP-MAVEN-CVE-2026-47892, UBUNTU-CVE-2026-47892 ## What is CVE-2026-47892? CVE-2026-47892 is a critical vulnerability in Vmware Spring Framework, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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 Weakness: CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2026-47892? 12 open source packages ship an affected version, including org.springframework:spring-webflux. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.springframework:spring-webflux` | Maven | From 5.2.5.RELEASE to 5.2.25.RELEASE | None | | `org.springframework:spring-webflux` | Maven | From 5.2.5.RELEASE to 5.2.25.RELEASE | None | | `org.springframework:spring-webflux` | Maven | From 5.3.0 to 5.3.49 | None | | `org.springframework:spring-webflux` | Maven | From 5.3.0 to 5.3.49 | None | | `org.springframework:spring-webflux` | Maven | From 6.0.0 to 6.0.30 | None | | `org.springframework:spring-webflux` | Maven | From 6.0.0 to 6.0.30 | None | | `org.springframework:spring-webflux` | Maven | From 6.1.0 to 6.1.28 | None | | `org.springframework:spring-webflux` | Maven | From 6.1.0 to 6.1.28 | None | | `org.springframework:spring-webflux` | Maven | From 6.2.0 to 6.2.19 | None | | `org.springframework:spring-webflux` | Maven | From 6.2.0 to 6.2.19 | None | | `org.springframework:spring-webflux` | Maven | From 7.0.0 | 7.0.9 | | `org.springframework:spring-webflux` | Maven | From 7.0.0 | 7.0.9 | Products: Vmware Spring Framework. ## How do I fix CVE-2026-47892? Upgrade org.springframework:spring-webflux to 7.0.9 or later. ## Is CVE-2026-47892 being exploited? There is no known exploitation of CVE-2026-47892 in the wild and no public exploit code. ## Other vulnerabilities in Vmware Spring Framework - [CVE-2026-47884](https://insights.sbomify.com/CVE-2026-47884/): Spring Framework Improper Path Limitation in XsltView (critical 9.8) - [CVE-2026-47890](https://insights.sbomify.com/CVE-2026-47890/): Spring Framework Server Sent Event stream corruption while rendering fragments (critical 9.8) - [CVE-2026-47891](https://insights.sbomify.com/CVE-2026-47891/): Spring Framework maxInMemorySize Bypassed in Jaxb2Decoder (critical 9.8) - [CVE-2026-59313](https://insights.sbomify.com/CVE-2026-59313/): Server Sent Event stream corruption in Spring MVC functional web framework (critical 9.8) - [CVE-2016-1000027](https://insights.sbomify.com/CVE-2016-1000027/): Pivotal Spring Framework contains unsafe Java deserialization methods (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-47892 and fix it if it is affected. What it is: CVE-2026-47892 is a critical vulnerability in Vmware Spring Framework, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-47892 in the wild and no public exploit code. Affected packages and fixed versions: - org.springframework:spring-webflux (Maven): affected from 5.2.5.RELEASE up to 5.2.25.RELEASE; no fix listed - org.springframework:spring-webflux (Maven): affected from 5.2.5.RELEASE up to 5.2.25.RELEASE; no fix listed - org.springframework:spring-webflux (Maven): affected from 5.3.0 up to 5.3.49; no fix listed - org.springframework:spring-webflux (Maven): affected from 5.3.0 up to 5.3.49; no fix listed - org.springframework:spring-webflux (Maven): affected from 6.0.0 up to 6.0.30; no fix listed - org.springframework:spring-webflux (Maven): affected from 6.0.0 up to 6.0.30; no fix listed - org.springframework:spring-webflux (Maven): affected from 6.1.0 up to 6.1.28; no fix listed - org.springframework:spring-webflux (Maven): affected from 6.1.0 up to 6.1.28; no fix listed - org.springframework:spring-webflux (Maven): affected from 6.2.0 up to 6.2.19; no fix listed - org.springframework:spring-webflux (Maven): affected from 6.2.0 up to 6.2.19; no fix listed - org.springframework:spring-webflux (Maven): affected from 7.0.0; fixed in 7.0.9 - org.springframework:spring-webflux (Maven): affected from 7.0.0; fixed in 7.0.9 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-47892/ (Markdown: https://insights.sbomify.com/CVE-2026-47892/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47892 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47892 - OSV: https://osv.dev/vulnerability/CVE-2026-47892 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-47892/ Summaries are generated and may contain mistakes; the official description above is the record.