Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-g5vr-rgqm-vf78

HIGH

Spring Framework Path Traversal vulnerability

Also known asCVE-2024-38819
Published
Dec 19, 2024
Updated
May 28, 2025
Affected
6 pkgs
Patched
2 / 6
Exploits
3 known

Blast Radius

6 pkgs affected
org.springframework:spring-webfluxorg.springframework:spring-webmvcorg.springframework:spring-webfluxorg.springframework:spring-webmvcorg.springframework:spring-webfluxorg.springframework:spring-webmvc

Real-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

Applications serving static resources through the functional web frameworks WebMvc.fn or WebFlux.fn are vulnerable to path traversal attacks. An attacker can craft malicious HTTP requests and obtain any file on the file system that is also accessible to the process in which the Spring application is running.

Affected Packages

6 total 2 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.springframework:spring-webflux6.1.0&&< 6.1.146.1.14
Mavenorg.springframework:spring-webmvc6.1.0&&< 6.1.146.1.14
Mavenorg.springframework:spring-webfluxall versionsNo fix
Mavenorg.springframework:spring-webmvcall versionsNo fix
Mavenorg.springframework:spring-webflux6.0.0No fix
Mavenorg.springframework:spring-webmvc6.0.0No fix
Exploits & PoCs
3

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework:spring-webflux. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.springframework:spring-webflux to 6.1.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g5vr-rgqm-vf78 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-g5vr-rgqm-vf78 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-g5vr-rgqm-vf78. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Applications serving static resources through the functional web frameworks WebMvc.fn or WebFlux.fn are vulnerable to path traversal attacks. An attacker can craft malicious HTTP requests and obtain any file on the file system that is also accessible to the process in which the Spring application is running.
O3 Security · Impact-Aware SCA

Is GHSA-g5vr-rgqm-vf78 in your dependencies?

O3 detects GHSA-g5vr-rgqm-vf78 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.