Is org.springframework:spring-webflux 6.0 vulnerable?
Maven · 24 releases from 6.0.0 to 6.0.23 · latest org.springframework:spring-webflux is 7.0.10 · checked 18 Nov 2026
Yes: 5 known advisories
Yes. org.springframework:spring-webflux 6.0.23, the last 6.0 release, is affected by 5 known security advisories (1 critical, 2 high, 1 medium, 1 low), including CVE-2026-47892, CVE-2024-38819, CVE-2024-38816. Upgrade to 7.0.9 or later to fix all of them.
mvn versions:use-dep-version -Dincludes=org.springframework:spring-webflux -DdepVersion=7.0.9 -DforceVersion=trueIs your project on an affected org.springframework:spring-webflux?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting org.springframework:spring-webflux 6.0.23
Spring Framework Header Predicate Bypass in WebFlux Functional Endpoints
- Affected
- >=5.2.5.RELEASE <=5.2.25.RELEASE · >=5.3.0 <=5.3.49 · >=6.0.0 <=6.0.30 · >=6.1.0 <=6.1.28 · >=6.2.0 <=6.2.19 · >=7.0.0 <7.0.9
- Fixed in
- 7.0.9
Spring Framework Improper Path Limitation with Script View Templates
- Affected
- >=7.0.0-M1 <7.0.6 · >=6.2.0 <6.2.17 · >=6.0.0 <=6.1.21 · >=5.3.0 <=5.3.39
- Fixed in
- 6.2.17, 7.0.6
Spring MVC and WebFlux has Server Sent Event stream corruption
- Affected
- >=7.0.0-M1 <7.0.6 · >=6.2.0 <6.2.17 · >=6.0.0 <=6.1.21 · >=5.3.0 <=5.3.39
- Fixed in
- 6.2.17, 7.0.6
Spring Framework Path Traversal vulnerability
- Affected
- >=6.1.0 <6.1.14 · <=5.3.40 · >=6.0.0 <=6.0.24
- Fixed in
- 6.1.14
Path traversal vulnerability in functional web frameworks
- Affected
- >=6.1.0 <6.1.13 · >=6.0.0 <=6.0.23 · >=5.3.0 <=5.3.39
- Fixed in
- 6.1.13
Every org.springframework:spring-webflux 6.0.x release
Affected: 6.0.0 to 6.0.23. Latest org.springframework:spring-webflux: 7.0.10.
| Version | Known advisories |
|---|---|
| org.springframework:spring-webflux 6.0.23 | CVE-2026-47892, CVE-2026-22737, CVE-2026-22735, CVE-2024-38819, CVE-2024-38816 |
| org.springframework:spring-webflux 6.0.22 | CVE-2026-47892, CVE-2026-22737, CVE-2026-22735, CVE-2024-38819, CVE-2024-38816 |
| org.springframework:spring-webflux 6.0.21 | CVE-2026-47892, CVE-2026-22737, CVE-2026-22735, CVE-2024-38819, CVE-2024-38816 |
| org.springframework:spring-webflux 6.0.20 | CVE-2026-47892, CVE-2026-22737, CVE-2026-22735, CVE-2024-38819, CVE-2024-38816 |
| org.springframework:spring-webflux 6.0.19 | CVE-2026-47892, CVE-2026-22737, CVE-2026-22735, CVE-2024-38819, CVE-2024-38816 |
| org.springframework:spring-webflux 6.0.18 | CVE-2026-47892, CVE-2026-22737, CVE-2026-22735, CVE-2024-38819, CVE-2024-38816 |
| org.springframework:spring-webflux 6.0.17 | CVE-2026-47892, CVE-2026-22737, CVE-2026-22735, CVE-2024-38819, CVE-2024-38816 |
| org.springframework:spring-webflux 6.0.16 | CVE-2026-47892, CVE-2026-22737, CVE-2026-22735, CVE-2024-38819, CVE-2024-38816 |
| org.springframework:spring-webflux 6.0.15 | CVE-2026-47892, CVE-2026-22737, CVE-2026-22735, CVE-2024-38819, CVE-2024-38816 |
| org.springframework:spring-webflux 6.0.14 | CVE-2026-47892, CVE-2026-22737, CVE-2026-22735, CVE-2024-38819, CVE-2024-38816 |
| org.springframework:spring-webflux 6.0.13 | CVE-2026-47892, CVE-2026-22737, CVE-2026-22735, CVE-2024-38819, CVE-2024-38816 |
| org.springframework:spring-webflux 6.0.12 | CVE-2026-47892, CVE-2026-22737, CVE-2026-22735, CVE-2024-38819, CVE-2024-38816 |
| org.springframework:spring-webflux 6.0.11 | CVE-2026-47892, CVE-2026-22737, CVE-2026-22735, CVE-2024-38819, CVE-2024-38816 |
| org.springframework:spring-webflux 6.0.10 | CVE-2026-47892, CVE-2026-22737, CVE-2026-22735, CVE-2024-38819, CVE-2024-38816 |
| org.springframework:spring-webflux 6.0.9 | CVE-2026-47892, CVE-2026-22737, CVE-2026-22735, CVE-2024-38819, CVE-2024-38816 |
| org.springframework:spring-webflux 6.0.8 | CVE-2026-47892, CVE-2026-22737, CVE-2026-22735, CVE-2024-38819, CVE-2024-38816 |
| org.springframework:spring-webflux 6.0.7 | CVE-2026-47892, CVE-2026-22737, CVE-2026-22735, CVE-2024-38819, CVE-2024-38816 |
| org.springframework:spring-webflux 6.0.6 | CVE-2026-47892, CVE-2026-22737, CVE-2026-22735, CVE-2024-38819, CVE-2024-38816 |
| org.springframework:spring-webflux 6.0.5 | CVE-2026-47892, CVE-2026-22737, CVE-2026-22735, CVE-2024-38819, CVE-2024-38816 |
| org.springframework:spring-webflux 6.0.4 | CVE-2026-47892, CVE-2026-22737, CVE-2026-22735, CVE-2024-38819, CVE-2024-38816 |
| org.springframework:spring-webflux 6.0.3 | CVE-2026-47892, CVE-2026-22737, CVE-2026-22735, CVE-2024-38819, CVE-2024-38816 |
| org.springframework:spring-webflux 6.0.2 | CVE-2026-47892, CVE-2026-22737, CVE-2026-22735, CVE-2024-38819, CVE-2024-38816 |
| org.springframework:spring-webflux 6.0.1 | CVE-2026-47892, CVE-2026-22737, CVE-2026-22735, CVE-2024-38819, CVE-2024-38816 |
| org.springframework:spring-webflux 6.0.0 | CVE-2026-47892, CVE-2026-22737, CVE-2026-22735, CVE-2024-38819, CVE-2024-38816 |
Which of your client projects are still on org.springframework:spring-webflux 6.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.springframework:spring-webflux version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other org.springframework:spring-webflux versions
- org.springframework:spring-webflux 7.0
- org.springframework:spring-webflux 6.2
- org.springframework:spring-webflux 6.1
- org.springframework:spring-webflux 5.3
- org.springframework:spring-webflux 5.2
- org.springframework:spring-webflux 5.1
- org.springframework:spring-webflux 5.0
- All org.springframework:spring-webflux advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.