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

CVE-2025-31651

CRITICAL

Apache Tomcat Rewrite rule bypass

Also known asBIT-tomcat-2025-31651GHSA-ff77-26x5-69cr
Published
Apr 28, 2025
Updated
Apr 16, 2026
Affected
8 pkgs
Patched
6 / 8
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
4.2%probability of exploitation in next 30 days
Lower Risk90th percentile+3.98%
0.00%1.81%3.61%5.42%0.1%4.2%Dec 25Apr 26Jun 26

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

8 pkgs affected
org.apache.tomcat:tomcat-catalinaorg.apache.tomcat:tomcat-catalinaorg.apache.tomcat:tomcat-catalinaorg.apache.tomcat.embed:tomcat-embed-coreorg.apache.tomcat.embed:tomcat-embed-coreorg.apache.tomcat.embed:tomcat-embed-coreorg.apache.tomcat:tomcat-catalinaorg.apache.tomcat.embed:tomcat-embed-core

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

Improper Neutralization of Escape, Meta, or Control Sequences vulnerability in Apache Tomcat. For a subset of unlikely rewrite rule configurations, it was possible for a specially crafted request to bypass some rewrite rules. If those rewrite rules effectively enforced security constraints, those constraints could be bypassed.

This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.5, from 10.1.0-M1 through 10.1.39, from 9.0.0.M1 through 9.0.102. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.0 though 8.5.100. Other, older, EOL versions may also be affected.

Users are recommended to upgrade to version [FIXED_VERSION], which fixes the issue.

Affected Packages

8 total 6 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.apache.tomcat:tomcat-catalina9.0.76&&< 9.0.1049.0.104
Mavenorg.apache.tomcat:tomcat-catalina10.1.10&&< 10.1.4010.1.40
Mavenorg.apache.tomcat:tomcat-catalina11.0.0-M2&&< 11.0.611.0.6
Mavenorg.apache.tomcat.embed:tomcat-embed-core9.0.76&&< 9.0.1049.0.104
Mavenorg.apache.tomcat.embed:tomcat-embed-core10.1.10&&< 10.1.4010.1.40
Mavenorg.apache.tomcat.embed:tomcat-embed-core11.0.0-M2&&< 11.0.611.0.6

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

Frequently Asked Questions

Improper Neutralization of Escape, Meta, or Control Sequences vulnerability in Apache Tomcat. For a subset of unlikely rewrite rule configurations, it was possible for a specially crafted request to bypass some rewrite rules. If those rewrite rules effectively enforced security constraints, those constraints could be bypassed. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.5, from 10.1.0-M1 through 10.1.39, from 9.0.0.M1 through 9.0.102. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.0 though 8.5.100. Other, older, EOL vers
O3 Security · Impact-Aware SCA

Is CVE-2025-31651 in your dependencies?

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