How severe is CVE-2026-34486?

CVE-2026-34486 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-34486?

CVE-2026-34486 affects the following packages: org.apache.tomcat:tomcat-tribes (Maven), org.apache.tomcat:tomcat-tribes (Maven), org.apache.tomcat:tomcat-tribes (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven). Ecosystems affected: Maven.

How do I fix CVE-2026-34486?

Update org.apache.tomcat:tomcat-tribes to 11.0.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-34486 is resolved across your whole dependency graph.

How do I detect CVE-2026-34486 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat-tribes. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2026-34486 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2026-34486?

O3 pinpoints whether CVE-2026-34486 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2026-34486 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-34486 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

Is CVE-2026-34486 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2026-34486 (Apache Tomcat Missing Encryption of Sensitive Data Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2026-08-04. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-08-07. The required action was: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2026-34486?

CVE-2026-34486 is classified as CWE-311 (CWE-311), CWE-807 (CWE-807). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2026-34486?

A Nuclei detection template exists for CVE-2026-34486, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2026-34486 published, and has it been updated?

CVE-2026-34486 was published on April 9, 2026 and was last updated on August 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2026-08-04 — agencies required to remediate by 2026-08-07

☕ Maven

CVE-2026-34486

HIGH

CVE-2026-34486 is a high-severity (CVSS 7.5) CWE-311 vulnerability in org.apache.tomcat:tomcat-tribes. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-08-04) — treat it as actively exploited and patch now. O3 Security confirms whether CVE-2026-34486 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Apache Tomcat: Fix for CVE-2026-29146 allowed bypass of EncryptInterceptor

Also known asBIT-tomcat-2026-34486GHSA-69r9-qgr7-g2wj

Published

Apr 9, 2026

Updated

Aug 7, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

Blast Radius

6 pkgs affected

☕org.apache.tomcat:tomcat-tribes☕org.apache.tomcat:tomcat-tribes☕org.apache.tomcat:tomcat-tribes☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat-tribes`	≥ 11.0.20&&< 11.0.21	11.0.21
☕Maven	`org.apache.tomcat:tomcat-tribes`	≥ 10.1.53&&< 10.1.54	10.1.54
☕Maven	`org.apache.tomcat:tomcat-tribes`	≥ 9.0.116&&< 9.0.117	9.0.117
☕Maven	`org.apache.tomcat:tomcat`	≥ 11.0.20&&< 11.0.21	11.0.21
☕Maven	`org.apache.tomcat:tomcat`	≥ 10.1.53&&< 10.1.54	10.1.54
☕Maven	`org.apache.tomcat:tomcat`	≥ 9.0.116&&< 9.0.117	9.0.117

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat-tribes. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.apache.tomcat:tomcat-tribes to 11.0.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-34486 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-34486 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2026-34486. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2026-34486 in your dependencies?

O3 detects CVE-2026-34486 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works