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

CVE-2024-52317

MEDIUM

CVE-2024-52317 is a medium-severity (CVSS 6.5) CWE-326 vulnerability in org.apache.tomcat.embed:tomcat-embed-core. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2024-52317 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Apache Tomcat: Request/response mix-up with HTTP/2

Also known asBIT-tomcat-2024-52317GHSA-qvf5-hvjx-wm27
Published
Nov 18, 2024
Updated
Jul 15, 2026
Affected
6 pkgs
Patched
6 / 6
Exploits
1 known

Blast Radius

6 pkgs affected
org.apache.tomcat.embed:tomcat-embed-coreorg.apache.tomcat:tomcat-coyoteorg.apache.tomcat.embed:tomcat-embed-coreorg.apache.tomcat.embed:tomcat-embed-coreorg.apache.tomcat:tomcat-coyoteorg.apache.tomcat:tomcat-coyote

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

Incorrect object re-cycling and re-use vulnerability in Apache Tomcat. Incorrect recycling of the request and response used by HTTP/2 requests could lead to request and/or response mix-up between users.

This issue affects Apache Tomcat: from 11.0.0-M23 through 11.0.0-M26, from 10.1.27 through 10.1.30, from 9.0.92 through 9.0.95.

Users are recommended to upgrade to version 11.0.0, 10.1.31 or 9.0.96, which fixes the issue.

Affected Packages

6 total 6 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.apache.tomcat.embed:tomcat-embed-core9.0.92&&< 9.0.969.0.96
Mavenorg.apache.tomcat:tomcat-coyote9.0.92&&< 9.0.969.0.96
Mavenorg.apache.tomcat.embed:tomcat-embed-core10.1.27&&< 10.1.3110.1.31
Mavenorg.apache.tomcat.embed:tomcat-embed-core11.0.0-M23&&< 11.0.011.0.0
Mavenorg.apache.tomcat:tomcat-coyote10.1.27&&< 10.1.3110.1.31
Mavenorg.apache.tomcat:tomcat-coyote11.0.0-M23&&< 11.0.011.0.0
Exploits & PoCs
1

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.apache.tomcat.embed:tomcat-embed-core. 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.apache.tomcat.embed:tomcat-embed-core to 9.0.96 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-52317 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 CVE-2024-52317 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-52317. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Incorrect object re-cycling and re-use vulnerability in Apache Tomcat. Incorrect recycling of the request and response used by HTTP/2 requests could lead to request and/or response mix-up between users. This issue affects Apache Tomcat: from 11.0.0-M23 through 11.0.0-M26, from 10.1.27 through 10.1.30, from 9.0.92 through 9.0.95. Users are recommended to upgrade to version 11.0.0, 10.1.31 or 9.0.96, which fixes the issue.
O3 Security · Impact-Aware SCA

Is CVE-2024-52317 in your dependencies?

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