NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕ Maven
Not in CISA KEV

Apache Tomcat - Security constraint bypass for pre/post-resourcesGHSA-wc4r-xq3c-5cf3

Fix: apache/tomcat@7617b9c

GHSA-wc4r-xq3c-5cf3 is a CWE-288 vulnerability in org.apache.tomcat:tomcat-catalina. A fix is available for org.apache.tomcat:tomcat-catalina — see the affected versions and patch details below.

Also known asBIT-tomcat-2025-49125CVE-2025-49125
Published
Updated
Affected
8 pkgs
Patched
6 / 8
Exploits
None indexed
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-wc4r-xq3c-5cf3.

EPSS Exploitation Probability

via FIRST.org ↗
3.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs89th percentile — riskier than 89% of all scored CVEsHighest risk
0.00%1.47%2.94%4.41%0.3%3.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

8 pkgs affected
☕org.apache.tomcat:tomcat-catalina☕org.apache.tomcat:tomcat-catalina☕org.apache.tomcat:tomcat-catalina☕org.apache.tomcat.embed:tomcat-embed-core☕org.apache.tomcat.embed:tomcat-embed-core☕org.apache.tomcat.embed:tomcat-embed-core☕org.apache.tomcat:tomcat-catalina☕org.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

Authentication Bypass Using an Alternate Path or Channel vulnerability in Apache Tomcat.  When using PreResources or PostResources mounted other than at the root of the web application, it was possible to access those resources via an unexpected path. That path was likely not to be protected by the same security constraints as the expected path, allowing those security constraints to be bypassed.

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

Users are recommended to upgrade to version 11.0.8, 10.1.42 or 9.0.106, which fix the issue.

Affected Packages

8 total 6 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.tomcat:tomcat-catalina≥ 11.0.0-M1&&< 11.0.811.0.8org.apache.tomcat:tomcat-catalina:11.0.8
☕Mavenorg.apache.tomcat:tomcat-catalina≥ 10.1.0-M1&&< 10.1.4210.1.42org.apache.tomcat:tomcat-catalina:10.1.42
☕Mavenorg.apache.tomcat:tomcat-catalina≥ 9.0.0.M1&&< 9.0.1069.0.106org.apache.tomcat:tomcat-catalina:9.0.106
☕Mavenorg.apache.tomcat.embed:tomcat-embed-core≥ 11.0.0-M1&&< 11.0.811.0.8org.apache.tomcat.embed:tomcat-embed-core:11.0.8
☕Mavenorg.apache.tomcat.embed:tomcat-embed-core≥ 10.1.0-M1&&< 10.1.4210.1.42org.apache.tomcat.embed:tomcat-embed-core:10.1.42
☕Mavenorg.apache.tomcat.embed:tomcat-embed-core≥ 9.0.0.M1&&< 9.0.1069.0.106org.apache.tomcat.embed:tomcat-embed-core:9.0.106

Affected Products

1 product · 3 configurations
Application
tomcatapache
≥ 11.0.0 && < 11.0.8
range

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.apache.tomcat:tomcat-catalina to 11.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wc4r-xq3c-5cf3 is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow
Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for GHSA-wc4r-xq3c-5cf3 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat Enterprise Linux 10tomcat9-1:9.0.87-5.el10_0.3RHSA-2025:14178
Red Hat Enterprise Linux 10tomcat-1:10.1.36-1.el10_0.2RHSA-2025:14179
Red Hat Enterprise Linux 8tomcat-1:9.0.87-1.el8_10.6RHSA-2025:14177
Red Hat Enterprise Linux 8.8 Telecommunications Update Servicetomcat-1:9.0.87-1.el8_8.7RHSA-2025:14182
Red Hat Enterprise Linux 9tomcat-1:9.0.87-3.el9_6.3RHSA-2025:14181
Red Hat Enterprise Linux 9.2 Update Services for SAP Solutionstomcat-1:9.0.87-1.el9_2.6RHSA-2025:14183
Red Hat Enterprise Linux 9.4 Extended Update Supporttomcat-1:9.0.87-1.el9_4.6RHSA-2025:14180
Red Hat JBoss Web Server 5.8.5tomcat-catalinaRHSA-2025:11696

Frequently Asked Questions

Authentication Bypass Using an Alternate Path or Channel vulnerability in Apache Tomcat.  When using PreResources or PostResources mounted other than at the root of the web application, it was possible to access those resources via an unexpected path. That path was likely not to be protected by the same security constraints as the expected path, allowing those security constraints to be bypassed. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.7, from 10.1.0-M1 through 10.1.41, from 9.0.0.M1 through 9.0.105. The following versions were EOL at the time the CVE was created but are
O3 Security · Impact-Aware SCA

Is GHSA-wc4r-xq3c-5cf3 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Apache Tomcat - Security constraint bypass for…