CVE-2026-34486
Apache Tomcat Missing Encryption of Sensitive Data Vulnerability
Apache Tomcat
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.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 4 August 2026. US federal agencies were required to remediate it by 7 August 2026.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 98.5%, which is higher than 99.9% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Frequently asked questions
Is CVE-2026-34486 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2026-34486.
What does CVE-2026-34486 affect?
CVE-2026-34486 affects Apache Tomcat. 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.
How severe is CVE-2026-34486?
CVE-2026-34486 is rated HIGH with a CVSS base score of 7.5. EPSS puts the probability of exploitation in the next 30 days at 98.5%, higher than 99.9% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 7 August 2026.
How should organisations respond to CVE-2026-34486?
Apply the vendor patch for Apache Tomcat as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.