How severe is CVE-2024-13009?

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

Which packages are affected by CVE-2024-13009?

CVE-2024-13009 affects the following packages: org.eclipse.jetty:jetty-server (Maven). Ecosystems affected: Maven.

How do I fix CVE-2024-13009?

Update org.eclipse.jetty:jetty-server to 9.4.57.v20241219 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-13009 is resolved across your whole dependency graph.

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

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.jetty:jetty-server. 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-13009 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-13009?

O3 pinpoints whether CVE-2024-13009 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-13009 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-13009 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 type of vulnerability is CVE-2024-13009?

CVE-2024-13009 is classified as CWE-404 (CWE-404). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2024-13009 was published on May 8, 2025 and was last updated on July 15, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

CVE-2024-13009

HIGH

CVE-2024-13009 is a high-severity (CVSS 7.2) CWE-404 vulnerability in org.eclipse.jetty:jetty-server. O3 Security confirms whether CVE-2024-13009 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Eclipse Jetty GZIP buffer release

Also known asGHSA-q4rv-gq96-w7c5

Published

May 8, 2025

Updated

Jul 15, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

☕org.eclipse.jetty:jetty-server

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 Eclipse Jetty versions 9.4.0 to 9.4.56 a buffer can be incorrectly released when confronted with a gzip error when inflating a request body. This can result in corrupted and/or inadvertent sharing of data between requests.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.eclipse.jetty:jetty-server`	≥ 9.4.0&&< 9.4.57.v20241219	9.4.57.v20241219

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.jetty:jetty-server. 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.eclipse.jetty:jetty-server to 9.4.57.v20241219 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-13009 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-13009 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-13009. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2024-13009 in your dependencies?

O3 detects CVE-2024-13009 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