How severe is CVE-2024-38819?

CVE-2024-38819 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2024-38819?

CVE-2024-38819 affects the following packages: org.springframework:spring-webflux (Maven), org.springframework:spring-webmvc (Maven), org.springframework:spring-webflux (Maven), org.springframework:spring-webmvc (Maven), org.springframework:spring-webflux (Maven), org.springframework:spring-webmvc (Maven). Ecosystems affected: Maven.

How do I fix CVE-2024-38819?

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 CVE-2024-38819 is resolved across your whole dependency graph.

How do I detect CVE-2024-38819 in my Maven dependencies?

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.

How do I mitigate CVE-2024-38819 if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against CVE-2024-38819?

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

Is CVE-2024-38819 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2024-38819, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2024-38819?

CVE-2024-38819 has an EPSS (Exploit Prediction Scoring System) score of 54.9%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2024-38819?

CVE-2024-38819 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2024-38819?

A Nuclei detection template exists for CVE-2024-38819, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2024-38819 published, and has it been updated?

CVE-2024-38819 was published on December 19, 2024 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2024-38819: Spring Framework Path Traversal vulnerability…

EPSS Exploitation Probability

via FIRST.org ↗

54.9%probability of exploitation in next 30 days

High Risk99th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

6 pkgs affected

☕org.springframework:spring-webflux☕org.springframework:spring-webmvc☕org.springframework:spring-webflux☕org.springframework:spring-webmvc☕org.springframework:spring-webflux☕org.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

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework:spring-webflux`	≥ 6.1.0&&< 6.1.14	6.1.14
☕Maven	`org.springframework:spring-webmvc`	≥ 6.1.0&&< 6.1.14	6.1.14
☕Maven	`org.springframework:spring-webflux`	all versions	No fix
☕Maven	`org.springframework:spring-webmvc`	all versions	No fix
☕Maven	`org.springframework:spring-webflux`	≥ 6.0.0	No fix
☕Maven	`org.springframework:spring-webmvc`	≥ 6.0.0	No fix

Detection & mitigation playbook

Open-source dependency

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.
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 CVE-2024-38819 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether CVE-2024-38819 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 CVE-2024-38819. 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 CVE-2024-38819 in your dependencies?

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

Scan my dependencies How O3 SCA works

CVE-2024-38819