CVE-2026-29146: Apache Tomcat: EncryptInterceptor vulnerable to padding oracle attack by default
Padding Oracle vulnerability in Apache Tomcat's EncryptInterceptor with default configuration.
This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.18, from 10.0.0-M1 through 10.1.52, from 9.0.13 through 9..115, from 8.5.38 through 8.5.100, from 7.0.100 through 7.0.109.
Users are recommended to upgrade to version 11.0.19, 10.1.53 and 9.0.116, which fixes the issue.
Security readout for executives and security teams
Apache Tomcat has a high-severity confidentiality flaw in EncryptInterceptor when used with its default configuration. An unauthenticated network attacker may be able to use padding-oracle behavior to recover protected information. Exposure depends on whether affected Tomcat versions use this interceptor, not merely whether Tomcat is installed. Highest concern is internet- or network-reachable Tomcat deployments running affected versions with EncryptInterceptor enabled using the default configuration. Environments not using EncryptInterceptor appear less exposed based on the provided description. Older 8.5 and 7 deployments require special attention because the bundle names affected ranges but only lists fixed versions for 11, 10.1, and 9. Treat as priority patching for any Tomcat systems using EncryptInterceptor, especially shared or externally reachable services. The urgency is high because exploitation is remote and unauthenticated, but scope should be validated before broad emergency action. Mitigation focus: Upgrade Tomcat 11 to 11.0.19 or later where applicable.; Upgrade Tomcat 10.1 to 10.1.53 or later where applicable.; Upgrade Tomcat 9 to 9.0.116 or later where applicable..
Prepared
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-1240: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
CWE-209: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.