# CVE-2025-55752: Apache Tomcat: Directory traversal via rewrite with possible RCE if PUT is enabled > Attackers can bypass security constraints via path traversal in rewritten URLs, potentially achieving remote code execution if PUT requests are enabled. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 27 Oct 2025 - **Updated:** 12 May 2026 - **Also known as:** BIT-tomcat-2025-55752, CLSA-2025-1765903038, CLSA-2025-1766534900, CLSA-2025-1767098873, CLSA-2026-1768989206, CLSA-2026-1773879448, DEBIAN-CVE-2025-55752, GHSA-wmwf-9ccg-fff5, ROOT-APP-MAVEN-CVE-2025-55752, UBUNTU-CVE-2025-55752 ## What is CVE-2025-55752? CVE-2025-55752 is a high-severity path traversal vulnerability in Apache Tomcat, published on 27 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Relative Path Traversal vulnerability in Apache Tomcat. The fix for bug 60013 introduced a regression where the rewritten URL was normalized before it was decoded. This introduced the possibility that, for rewrite rules that rewrite query parameters to the URL, an attacker could manipulate the request URI to bypass security constraints including the protection for /WEB-INF/ and /META-INF/. If PUT requests were also enabled then malicious files could be uploaded leading to remote code execution. PUT requests are normally limited to trusted users and it is considered unlikely that PUT requests would be enabled in conjunction with a rewrite that manipulated the URI. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.10, from 10.1.0-M1 through 10.1.44, from 9.0.0.M11 through 9.0.108. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.6 though 8.5.100. Other, older, EOL versions may also be affected. Users are recommended to upgrade to version 11.0.11 or later, 10.1.45 or later or 9.0.109 or later, which fix the issue. Weakness: CWE-23 (Relative Path Traversal) ## Which versions are affected by CVE-2025-55752? 25 open source packages ship an affected version, including org.apache.tomcat.embed:tomcat-embed-core, tomcat and org.apache.tomcat:tomcat. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 10.1.0-M1 | 10.1.45 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 10.1.0-M1 | 10.1.45 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 11.0.0-M1 | 11.0.11 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 11.0.0-M1 | 11.0.11 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.5.6 to 8.5.100 | None | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.5.6 to 8.5.100 | None | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 9.0.0-M11 | 9.0.109 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 9.0.0-M11 | 9.0.109 | | `tomcat` | Bitnami | All versions | 9.0.109, 10.1.45, 11.0.11 | | `org.apache.tomcat:tomcat` | Maven | From 10.1.0-M1 | 10.1.45 | | `org.apache.tomcat:tomcat` | Maven | From 10.1.0-M1 | 10.1.45 | | `org.apache.tomcat:tomcat` | Maven | From 11.0.0-M1 | 11.0.11 | | `org.apache.tomcat:tomcat` | Maven | From 11.0.0-M1 | 11.0.11 | | `org.apache.tomcat:tomcat` | Maven | From 8.5.6 to 8.5.100 | None | | `org.apache.tomcat:tomcat` | Maven | From 8.5.6 to 8.5.100 | None | | `org.apache.tomcat:tomcat` | Maven | From 9.0.0-M11 | 9.0.109 | | `org.apache.tomcat:tomcat` | Maven | From 9.0.0-M11 | 9.0.109 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 10.1.0-M1 | 10.1.45 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 10.1.0-M1 | 10.1.45 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 11.0.0-M1 | 11.0.11 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 11.0.0-M1 | 11.0.11 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 8.5.6 to 8.5.100 | None | | `org.apache.tomcat:tomcat-catalina` | Maven | From 8.5.6 to 8.5.100 | None | | `org.apache.tomcat:tomcat-catalina` | Maven | From 9.0.0-M11 | 9.0.109 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 9.0.0-M11 | 9.0.109 | Products: Apache Tomcat. ## How do I fix CVE-2025-55752? Upgrade org.apache.tomcat.embed:tomcat-embed-core to a fixed version for your release line: 10.1.45, 11.0.11 or 9.0.109. ## Is CVE-2025-55752 being exploited? There is no known exploitation of CVE-2025-55752 in the wild and no public exploit code. Public exploit code: - CVE-2025-55752, Apache Tomcat that allows directory traversal via URL rewrite, and under certain conditions, leads to remote code execution (RCE) if HTTP PUT is enabled. (github_poc): https://github.com/TAM-K592/CVE-2025-55752 - https://github.com/masahiro331/CVE-2025-55752 (github_poc): https://github.com/masahiro331/CVE-2025-55752 - 基于 Docker 的重现环境，用于复现 Apache Tomcat 10.1.44 中的路径遍历漏洞 CVE-2025-55752。本实验场景可以复现官网报道的RCE (github_poc): https://github.com/AuroraSec-Pivot/CVE-2025-55752 - https://github.com/Jimmy01240397/CVE-2025-55752 (github_poc): https://github.com/Jimmy01240397/CVE-2025-55752 - CVE-2025-55752:Tomcat 8.5 已 EOL,终版 8.5.100。Apache 逐条声明「8.5 也受影响」的 2025 CVE 有 14 条,其中 10 条在 NVD 按 8.5.100 查不到。离线单 jar,读 conf/ 判断你到底中了哪几条。 (github_poc): https://github.com/xiaoqiMikko/tomcat85-check ## Other vulnerabilities in Apache Tomcat - [CVE-2025-24813](https://insights.sbomify.com/CVE-2025-24813/): Apache Tomcat Path Equivalence (critical 10.0, exploited in the wild) - [CVE-2016-8735](https://insights.sbomify.com/CVE-2016-8735/): Apache Tomcat Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2017-12617](https://insights.sbomify.com/CVE-2017-12617/): Apache Tomcat Remote Code Execution (high 8.1, exploited in the wild) - [CVE-2017-12615](https://insights.sbomify.com/CVE-2017-12615/): Apache Tomcat on Windows Remote Code Execution (high 8.1, exploited in the wild) - [CVE-2026-34486](https://insights.sbomify.com/CVE-2026-34486/): Apache Tomcat Missing Encryption of Sensitive Data (high 7.5, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-55752 and fix it if it is affected. What it is: CVE-2025-55752 is a high-severity path traversal vulnerability in Apache Tomcat, published on 27 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-55752 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 10.1.0-M1; fixed in 10.1.45 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 10.1.0-M1; fixed in 10.1.45 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 11.0.0-M1; fixed in 11.0.11 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 11.0.0-M1; fixed in 11.0.11 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.5.6 up to 8.5.100; no fix listed - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.5.6 up to 8.5.100; no fix listed - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 9.0.0-M11; fixed in 9.0.109 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 9.0.0-M11; fixed in 9.0.109 - tomcat (Bitnami): affected all versions; fixed in 9.0.109, 10.1.45, 11.0.11 - org.apache.tomcat:tomcat (Maven): affected from 10.1.0-M1; fixed in 10.1.45 - org.apache.tomcat:tomcat (Maven): affected from 10.1.0-M1; fixed in 10.1.45 - org.apache.tomcat:tomcat (Maven): affected from 11.0.0-M1; fixed in 11.0.11 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-55752/ (Markdown: https://insights.sbomify.com/CVE-2025-55752/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-55752 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-55752 - OSV: https://osv.dev/vulnerability/CVE-2025-55752 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-55752/ Summaries are generated and may contain mistakes; the official description above is the record.