How severe is GHSA-xjhv-p3fv-x24r?

GHSA-xjhv-p3fv-x24r has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-xjhv-p3fv-x24r?

GHSA-xjhv-p3fv-x24r affects the following packages: io.projectreactor.netty:reactor-netty-http (Maven), io.projectreactor.netty:reactor-netty-http (Maven). Ecosystems affected: Maven.

How do I fix GHSA-xjhv-p3fv-x24r?

Update io.projectreactor.netty:reactor-netty-http to 1.1.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xjhv-p3fv-x24r is resolved across your whole dependency graph.

How do I detect GHSA-xjhv-p3fv-x24r in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.projectreactor.netty:reactor-netty-http. 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 GHSA-xjhv-p3fv-x24r 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 GHSA-xjhv-p3fv-x24r?

O3 pinpoints whether GHSA-xjhv-p3fv-x24r 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 GHSA-xjhv-p3fv-x24r actively exploited in the wild?

No public exploit code has been indexed for GHSA-xjhv-p3fv-x24r yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-xjhv-p3fv-x24r?

GHSA-xjhv-p3fv-x24r has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 62th 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. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-xjhv-p3fv-x24r?

GHSA-xjhv-p3fv-x24r 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.

When was GHSA-xjhv-p3fv-x24r published, and has it been updated?

GHSA-xjhv-p3fv-x24r was published on November 15, 2023 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-xjhv-p3fv-x24r: reactor-netty-http Path Traversal (High 7.…

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk62th percentile-0.35%

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

2 pkgs affected

☕io.projectreactor.netty:reactor-netty-http☕io.projectreactor.netty:reactor-netty-http

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

In Reactor Netty HTTP Server, versions 1.1.x prior to 1.1.13 and versions 1.0.x prior to 1.0.39, a malicious user can send a request using a specially crafted URL that can lead to a directory traversal attack.

Specifically, an application is vulnerable if Reactor Netty HTTP Server is configured to serve static resources.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.projectreactor.netty:reactor-netty-http`	≥ 1.1.0&&< 1.1.13	1.1.13
☕Maven	`io.projectreactor.netty:reactor-netty-http`	≥ 1.0.0&&< 1.0.39	1.0.39

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.projectreactor.netty:reactor-netty-http. 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 io.projectreactor.netty:reactor-netty-http to 1.1.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xjhv-p3fv-x24r 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 GHSA-xjhv-p3fv-x24r 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-xjhv-p3fv-x24r. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In Reactor Netty HTTP Server, versions 1.1.x prior to 1.1.13 and versions 1.0.x prior to 1.0.39, a malicious user can send a request using a specially crafted URL that can lead to a directory traversal attack. Specifically, an application is vulnerable if Reactor Netty HTTP Server is configured to serve static resources.

O3 Security · Impact-Aware SCA

Is GHSA-xjhv-p3fv-x24r in your dependencies?

O3 detects GHSA-xjhv-p3fv-x24r 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

GHSA-xjhv-p3fv-x24r