Loading story…
Apache Tomcat disclosed CVE-2015-5345, a low-severity information-disclosure flaw that lets unauthenticated users determine whether protected directories or web-application roots exist. Tomcat processed redirects for directory URLs missing a trailing slash before applying security constraints, exposing the presence of resources that should not be discoverable.
Apache corrected the request-processing order by moving redirect handling into DefaultServlet, ensuring security constraints and enforcement filters are evaluated before redirects occur. Organizations should upgrade to Tomcat 6.0.45, 7.0.67, 8.0.30, 9.0.0.M3, or later.
See affected versions and whether adversaries are exploiting it.
2 events from the most recent confirmed update back to the earliest known activity.
Apache initially set mapperContextRootRedirectEnabled and mapperDirectoryRedirectEnabled to false to improve security, then changed mapperContextRootRedirectEnabled to true after judging regressions, including Bug 58765, more serious than the associated disclosure risk.
Apache corrected CVE-2015-5345 by moving trailing-slash redirect handling to DefaultServlet so security constraints and security-enforcing filters are evaluated before a redirect. The issue allowed unauthorised users to determine whether protected directories or web application root paths existed.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Apache Tomcat contained a limited directory-traversal flaw, tracked as **CVE-2015-5174**, in `RequestUtil.java`. Improper validation in the `ServletContext` `getResource()`, `getResourceAsStream()`, and `getResourcePaths()` methods allowed a `/..` path component during web-application resource lookups. A remote authenticated user controlling a malicious web application could exploit the issue under a Java SecurityManager to enumerate the application deployment parent directory, typically `$CATALINA_BASE/webapps`, bypassing intended restrictions. Apache corrected the flaw in Tomcat 6.0.45, 7.0.65, and 8.0.27; Tomcat 9 is not affected.
Aug 29, 2026
Apache Tomcat has remediated **CVE-2026-65182**, a critical improper authorization and access-control flaw (**CVSS 9.1**) that can let an unauthenticated remote attacker bypass configured security constraints. The issue arises when a constraint for a longer URL path is declared before a more restrictive constraint for a shorter subpath, causing Tomcat to apply access controls incorrectly. No public exploitation was known at the time of the notices. Affected releases include Tomcat 7.0.0–7.0.109, 8.5.0–8.5.100, 9.0.0.M1–9.0.120, 10.1.0-M1–10.1.57, and 11.0.0-M1–11.0.24, including deployments using embedded Tomcat libraries. Organizations should identify exposed instances and update to fixed releases—Tomcat 9.0.121, 10.1.58 or later, and 11.0.25 or later—while validating URL security-constraint ordering after remediation.
Sep 3, 2026
Apache Tomcat's `doRead` error handling flaw, tracked as **CVE-2008-4308**, can cause POST content from one HTTP request to be sent with a different request. The information-disclosure issue affects Tomcat versions 4.1.32 through 4.1.34 and 5.5.10 through 5.5.20; it results from `doRead` failing to return `-1` under a particular error condition. Apache's Tomcat 4.x vulnerability documentation continues to list this and other historical flaws affecting the obsolete 4.0.x and 4.1.x branches, including disclosure, denial-of-service, traversal, XSS, session-hijacking, and security-manager-bypass issues. Those branches are unsupported and will not receive further security fixes; organizations running affected releases should upgrade to a supported Tomcat version, at minimum Tomcat 7.x or later as advised in the documentation.
Aug 29, 2026