Apache Tomcat up to 7.0.109/8.5.100/9.0.115/10.1.52/11.0.18 EncryptInterceptor reliance on obfuscation or encryption of security-relevant inputs without integrity checking

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.6 | $0-$5k | 0.70- |
Summary
A vulnerability has been found in Apache Tomcat up to 7.0.109/8.5.100/9.0.115/10.1.52/11.0.18 and classified as problematic. Affected by this vulnerability is an unknown functionality of the component EncryptInterceptor. This manipulation causes reliance on obfuscation or encryption of security-relevant inputs without integrity checking. This vulnerability appears as CVE-2026-29146. The attack may be initiated remotely. There is no available exploit. The affected component should be upgraded.
Details
A vulnerability classified as problematic was found in Apache Tomcat up to 7.0.109/8.5.100/9.0.115/10.1.52/11.0.18. Affected by this vulnerability is an unknown part of the component EncryptInterceptor. The manipulation with an unknown input leads to a reliance on obfuscation or encryption of security-relevant inputs without integrity checking vulnerability. The CWE definition for the vulnerability is CWE-649. The product uses obfuscation or encryption of inputs that should not be mutable by an external actor, but the product does not use integrity checks to detect if those inputs have been modified. As an impact it is known to affect confidentiality. The summary by CVE is:
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.
The weakness was presented by Uri Katz and Avi Lumelsky. The advisory is shared at lists.apache.org. This vulnerability is known as CVE-2026-29146 since 03/04/2026. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/09/2026).
Upgrading to version 9.0.116, 10.1.53 or 11.0.19 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 7.0.109
- 8.0
- 8.1
- 8.2
- 8.3
- 8.4
- 8.5.100
- 9.0.115
- 10.1.0
- 10.1.1
- 10.1.2
- 10.1.3
- 10.1.4
- 10.1.5
- 10.1.6
- 10.1.7
- 10.1.8
- 10.1.9
- 10.1.10
- 10.1.11
- 10.1.12
- 10.1.13
- 10.1.14
- 10.1.15
- 10.1.16
- 10.1.17
- 10.1.18
- 10.1.19
- 10.1.20
- 10.1.21
- 10.1.22
- 10.1.23
- 10.1.24
- 10.1.25
- 10.1.26
- 10.1.27
- 10.1.28
- 10.1.29
- 10.1.30
- 10.1.31
- 10.1.32
- 10.1.33
- 10.1.34
- 10.1.35
- 10.1.36
- 10.1.37
- 10.1.38
- 10.1.39
- 10.1.40
- 10.1.41
- 10.1.42
- 10.1.43
- 10.1.44
- 10.1.45
- 10.1.46
- 10.1.47
- 10.1.48
- 10.1.49
- 10.1.50
- 10.1.51
- 10.1.52
- 11.0.0
- 11.0.1
- 11.0.2
- 11.0.3
- 11.0.4
- 11.0.5
- 11.0.6
- 11.0.7
- 11.0.8
- 11.0.9
- 11.0.10
- 11.0.11
- 11.0.12
- 11.0.13
- 11.0.14
- 11.0.15
- 11.0.16
- 11.0.17
- 11.0.18
License
Website
- Vendor: https://www.apache.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.7VulDB Meta Temp Score: 3.6
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Reliance on obfuscation or encryption of security-relevant inputs without integrity checkingCWE: CWE-649 / CWE-325
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Tomcat 9.0.116/10.1.53/11.0.19
Timeline
03/04/2026 CVE reserved04/09/2026 Advisory disclosed
04/09/2026 VulDB entry created
04/09/2026 VulDB entry last update
Sources
Vendor: apache.orgAdvisory: lists.apache.org
Researcher: Uri Katz, Avi Lumelsky
Status: Confirmed
CVE: CVE-2026-29146 (🔒)
GCVE (CVE): GCVE-0-2026-29146
GCVE (VulDB): GCVE-100-356653
Entry
Created: 04/09/2026 21:59Changes: 04/09/2026 21:59 (56)
Complete: 🔍
Cache ID: 216:2A5:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.