Loading story…
Apache Tomcat JK Web Server Connector (mod_jk) versions 1.2.x before 1.2.23 contain a directory-traversal and authorization-bypass flaw tracked as CVE-2007-1860. The issue arises because Apache HTTP Server decodes a request URL before passing it to Tomcat, allowing the two components to interpret the path differently.
A remote attacker could craft requests using a JkMount prefix, including double-encoded .. path sequences, to bypass access controls and reach protected pages. Organizations using affected mod_jk deployments should upgrade to version 1.2.23 or later and review exposed mounted paths and authorization rules for potential unauthorized access.
See affected versions and whether adversaries are exploiting it.
1 event from the most recent confirmed update back to the earliest known activity.
CVE-2007-1860 was published for a directory-traversal and authorization-bypass flaw in Apache Tomcat JK Web Server Connector (mod_jk) 1.2.x before 1.2.23. Crafted JkMount prefixes, including potentially double-encoded ".." sequences, could allow remote access to protected pages.
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.
A directory-traversal flaw tracked as **CVE-2007-0450** affects Apache HTTP Server deployments that proxy requests to vulnerable Apache Tomcat instances through `mod_proxy`, `mod_rewrite`, or `mod_jk`. The inconsistency arises because Tomcat treats forward slashes, backslashes, and URL-encoded backslashes as path separators differently from Apache HTTP Server. A remote attacker can send crafted `..` path sequences using these alternate separators to bypass path restrictions and read arbitrary files accessible to the Tomcat process. Affected versions include Tomcat 5.x before 5.5.22 and Tomcat 6.x before 6.0.10; organizations using the affected proxy configurations should upgrade Tomcat and review exposed applications for traversal attempts.
Aug 29, 2026
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