dbcve.org
TomcatWeb server / proxy · Apache

CVE-2025-49125

HIGH · 7.5 CVSS v3.1 Published 2025-06-16
Fix available
A fix is available. Upgrade to 9.0.106 / 10.1.42 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Tomcat contains an authentication bypass vulnerability where PreResources or PostResources mounted at non-root paths of a web application can be accessed via unexpected paths. These alternate paths likely lack the security constraints applied to the expected paths, allowing attackers to bypass authentication and authorization controls.

MitigationUpgrade Apache Tomcat to version 11.0.8, 10.1.42, or 9.0.106. If upgrading is not immediately feasible, review and ensure all resource mount points have appropriate security constraints applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TomcatWeb server / proxy
Affected:>= 9.0.0, < 9.0.106>= 10.1.0, < 10.1.42>= 11.0.0, < 11.0.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Tomcat version
    Check the version.jar or release file in your Tomcat installation, or run 'java -cp tomcat.jar org.apache.catalina.util.ServerInfo' from the Tomcat bin directory
    Affected if The installed version is 9.0.0 through 9.0.105, 10.1.0 through 10.1.41, or 11.0.0 through 11.0.7
  2. Locate web.xml configuration files
    Find the conf/web.xml file and any application-specific web.xml files in WEB-INF/ directories of deployed web applications
    Affected if The application uses PreResources or PostResources configuration elements
  3. Identify PreResources and PostResources configurations
    Search web.xml files for <pre-resources> and <post-resources> elements, and check context.xml for Resource definitions with url-pattern attributes
    Affected if Resources are defined with url-pattern attributes pointing to paths other than '/' (root)
  4. Verify security constraint coverage
    Review the <security-constraint> elements in web.xml and compare the defined web-resource-collection paths against all paths where PreResources or PostResources are accessible
    Affected if Security constraints do not explicitly cover all paths where PreResources or PostResources are mounted, or no security constraint exists for those paths
  5. Test alternate path access
    If PreResources or PostResources are mounted at /example, attempt to access /example/ and /example (without trailing slash) to verify if both paths behave identically regarding authentication
    Affected if One path requires authentication while the other does not, indicating the bypass is present

You are affected if your Tomcat version falls within the affected ranges AND you have PreResources or PostResources configured at non-root paths without comprehensive security constraints covering all accessible alternate path variations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.0.106 / 10.1.42 / 11.0.8 or later
Fixed in 9.0.10610.1.4211.0.8
Interim mitigation

Upgrade Apache Tomcat to version 11.0.8, 10.1.42, or 9.0.106. If upgrading is not immediately feasible, review and ensure all resource mount points have appropriate security constraints applied.

Recommended fix High confidence

9.0.106 for Tomcat 9.x, 10.1.42 for Tomcat 10.1.x, or 11.0.8 for Tomcat 11.x

  1. Identify the current Apache Tomcat version by checking the $CATALINA_HOME/README file or running 'catalina.sh version'
  2. Determine the appropriate upgrade path based on current major version: upgrade to 9.0.106 if on 9.x, 10.1.42 if on 10.1.x, or 11.0.8 if on 11.x
  3. Stop the Tomcat service or process
  4. Backup the entire Tomcat installation directory including conf/ and any deployed web applications
  5. Download the corresponding fixed release from https://tomcat.apache.org/download-90.cgi (9.0.106), https://tomcat.apache.org/download-110.cgi (10.1.42), or https://tomcat.apache.org/download-110.cgi (11.0.8)
  6. Extract the new version to a temporary location
  7. Copy the new Tomcat files over the old installation, preserving conf/ directory contents
  8. Restore any custom configuration from the backup if needed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tomcat Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49125 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-49125 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data