# CVE-2026-34486: Apache Tomcat Missing Encryption of Sensitive Data > Attackers can bypass the EncryptInterceptor in Apache Tomcat, potentially exposing sensitive data if encryption is enabled. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Yes, since 4 Aug 2026 (CISA KEV) - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 9 Apr 2026 - **Updated:** 21 Sep 2026 - **Also known as:** BIT-tomcat-2026-34486, CLSA-2026-1786391661, GHSA-69r9-qgr7-g2wj, ROOT-APP-MAVEN-CVE-2026-34486, UBUNTU-CVE-2026-34486 ## What is CVE-2026-34486? CVE-2026-34486 is a high-severity vulnerability in Apache Tomcat, published on 9 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Missing Encryption of Sensitive Data vulnerability in Apache Tomcat due to the fix for CVE-2026-29146 allowing the bypass of the EncryptInterceptor. This issue affects Apache Tomcat: 11.0.20, 10.1.53, 9.0.116. Users are recommended to upgrade to version 11.0.21, 10.1.54 or 9.0.117, which fix the issue. Weakness: CWE-807 (Reliance on Untrusted Inputs in a Security Decision), CWE-311 (Missing Encryption of Sensitive Data) ## Which versions are affected by CVE-2026-34486? 13 open source packages ship an affected version, including org.apache.tomcat:tomcat, tomcat and org.apache.tomcat:tomcat-tribes. It affects 7 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.tomcat:tomcat` | Maven | From 10.1.53 | 10.1.54 | | `org.apache.tomcat:tomcat` | Maven | From 10.1.53 | 10.1.54 | | `org.apache.tomcat:tomcat` | Maven | From 11.0.20 | 11.0.21 | | `org.apache.tomcat:tomcat` | Maven | From 11.0.20 | 11.0.21 | | `org.apache.tomcat:tomcat` | Maven | From 9.0.116 | 9.0.117 | | `org.apache.tomcat:tomcat` | Maven | From 9.0.116 | 9.0.117 | | `tomcat` | Bitnami | From 9.0.116 | 9.0.117, 10.1.54, 11.0.21 | | `org.apache.tomcat:tomcat-tribes` | Maven | From 10.1.53 | 10.1.54 | | `org.apache.tomcat:tomcat-tribes` | Maven | From 10.1.53 | 10.1.54 | | `org.apache.tomcat:tomcat-tribes` | Maven | From 11.0.20 | 11.0.21 | | `org.apache.tomcat:tomcat-tribes` | Maven | From 11.0.20 | 11.0.21 | | `org.apache.tomcat:tomcat-tribes` | Maven | From 9.0.116 | 9.0.117 | | `org.apache.tomcat:tomcat-tribes` | Maven | From 9.0.116 | 9.0.117 | Products: Apache Tomcat, Redhat Enterprise Linux, Redhat Enterprise Linux Els, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Tus, Redhat Enterprise Linux Update Services for Sap Solutions, Redhat Jboss Web Server. ## How do I fix CVE-2026-34486? Upgrade org.apache.tomcat:tomcat to a fixed version for your release line: 10.1.54, 11.0.21 or 9.0.117. US federal agencies must fix it by 7 Aug 2026. ## Is CVE-2026-34486 being exploited? Yes. Attackers have exploited CVE-2026-34486 in the wild since at least 4 Aug 2026. Public exploit code: - EncryptInterceptor fail-open bypass in Apache Tomcat Tribes clustering leading to unauthenticated RCE via Java deserialization. (github_poc): https://github.com/striga-ai/CVE-2026-34486 - CVE-2026-34486 Apache Tomcat EncryptInterceptor 绕过漏洞复现（使用GLM5.1复现完成） (github_poc): https://github.com/AirSkye/CVE-2026-34486-poc - Apache Tomcat EncryptInterceptor Bypass → Unauthenticated RCE (CVE-2026-34486) (github_poc): https://github.com/404-src/CVE-2026-34486 - CVE Reproduction: cve-2026-34486-tomcat_encrypt_bypass_reproduction (github_poc): https://github.com/razureink/cve-2026-34486-tomcat_encrypt_bypass_reproduction - EncryptInterceptor fail-open bypass in Apache Tomcat Tribes clustering leading to unauthenticated RCE via Java deserialization. (github_poc): https://github.com/CypherHippie/CVE-2026-34486---unauthenticated-RCE-via-Java-deserialization - Apache Tomcat Tribes EncryptInterceptor Bypass - Remote Code Execution (nuclei): http/cves/2026/CVE-2026-34486.yaml ## 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-65637](https://insights.sbomify.com/CVE-2026-65637/): Apache Tomcat: HTTP/2 no-authority bypass of strict SNI validation - CVE-2026-32990 fix incomplete (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-34486 and fix it if it is affected. What it is: CVE-2026-34486 is a high-severity vulnerability in Apache Tomcat, published on 9 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: Yes. Attackers have exploited CVE-2026-34486 in the wild since at least 4 Aug 2026. Affected packages and fixed versions: - org.apache.tomcat:tomcat (Maven): affected from 10.1.53; fixed in 10.1.54 - org.apache.tomcat:tomcat (Maven): affected from 10.1.53; fixed in 10.1.54 - org.apache.tomcat:tomcat (Maven): affected from 11.0.20; fixed in 11.0.21 - org.apache.tomcat:tomcat (Maven): affected from 11.0.20; fixed in 11.0.21 - org.apache.tomcat:tomcat (Maven): affected from 9.0.116; fixed in 9.0.117 - org.apache.tomcat:tomcat (Maven): affected from 9.0.116; fixed in 9.0.117 - tomcat (Bitnami): affected from 9.0.116; fixed in 9.0.117, 10.1.54, 11.0.21 - org.apache.tomcat:tomcat-tribes (Maven): affected from 10.1.53; fixed in 10.1.54 - org.apache.tomcat:tomcat-tribes (Maven): affected from 10.1.53; fixed in 10.1.54 - org.apache.tomcat:tomcat-tribes (Maven): affected from 11.0.20; fixed in 11.0.21 - org.apache.tomcat:tomcat-tribes (Maven): affected from 11.0.20; fixed in 11.0.21 - org.apache.tomcat:tomcat-tribes (Maven): affected from 9.0.116; fixed in 9.0.117 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-2026-34486/ (Markdown: https://insights.sbomify.com/CVE-2026-34486/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-34486 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-34486 - OSV: https://osv.dev/vulnerability/CVE-2026-34486 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-34486/ Summaries are generated and may contain mistakes; the official description above is the record.