Advisory record · GHSA-wc4r-xq3c-5cf3

Apache Tomcat - Security constraint bypass for pre/post-resources

CVSS 7.5 HighEPSS 0.026 · 85th percentile

Published by the GitHub Advisory Database at 16 Jun 2025, 15:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.apache.tomcat:tomcat-catalinaMaven>=11.0.0-M1, <11.0.8 || >=10.1.0-M1, <10.1.42 || >=9.0.0.M1, <9.0.106 || >=8.5.0, <=8.5.10011.0.8, 10.1.42, 9.0.106
org.apache.tomcat.embed:tomcat-embed-coreMaven>=11.0.0-M1, <11.0.8 || >=10.1.0-M1, <10.1.42 || >=9.0.0.M1, <9.0.106 || >=8.5.0, <=8.5.10011.0.8, 10.1.42, 9.0.106
Identifiers
GHSA-wc4r-xq3c-5cf3 · BIT-tomcat-2025-49125 · CVE-2025-49125
Weakness (CWE)
CWE-288
Published
16 Jun 2025
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Apache Tomcat versions 8.5.0 through 8.5.100, 9.0.0.M1 through 9.0.105, 10.1.0-M1 through 10.1.41, and 11.0.0-M1 through 11.0.7 are affected when PreResources or PostResources are mounted somewhere other than the web application root. An attacker can reach those resources through an unexpected path that may not be covered by the same security constraints, bypassing them. Upgrade to Tomcat 11.0.8, 10.1.42, or 9.0.106.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N ADP (CISA-ADP)
  • CISA KEV Not listed.
  • EPSS 0.026, the 85th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:17 UTC First seen by agentprime
  2. 31 Oct 2026, 14:17 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.