GHSA-69r9-qgr7-g2wj BIT-tomcat-2026-34486 CVE-2026-34486
Apache Tomcat Missing Encryption of Sensitive Data vulnerability
High
Known exploited
Maven
- Severity
- 7.5 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 98.50%
- Chance of exploitation in the next 30 days. Higher than 99.92% of scored vulnerabilities.
- Known exploited
- Yes
- In CISA's catalog since Aug 4, 2026
- Weakness
- CWE-311 Missing Encryption of Sensitive Data
- Fix
- Available
- 2 packages have a fixed version
Exploited in the wild. Apache Tomcat Missing Encryption of Sensitive Data Vulnerability (Apache Tomcat). Required action: 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. Due for U.S. federal agencies by Aug 7, 2026.
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 versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| org.apache.tomcat:tomcat | 1 listed versions | No fix yet |
| org.apache.tomcat:tomcat | 1 listed versions | No fix yet |
| org.apache.tomcat:tomcat | 1 listed versions | No fix yet |
| org.apache.tomcat:tomcat | >= 11.0.20, < 11.0.21 |
11.0.21 |
| org.apache.tomcat:tomcat | >= 10.1.53, < 10.1.54 |
10.1.54 |
| org.apache.tomcat:tomcat | >= 9.0.116, < 9.0.117 |
9.0.117 |
| org.apache.tomcat:tomcat-tribes | 1 listed versions | No fix yet |
| org.apache.tomcat:tomcat-tribes | 1 listed versions | No fix yet |
| org.apache.tomcat:tomcat-tribes | 1 listed versions | No fix yet |
| org.apache.tomcat:tomcat-tribes | >= 11.0.20, < 11.0.21 |
11.0.21 |
| org.apache.tomcat:tomcat-tribes | >= 10.1.53, < 10.1.54 |
10.1.54 |
| org.apache.tomcat:tomcat-tribes | >= 9.0.116, < 9.0.117 |
9.0.117 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
org.apache.tomcat:tomcat Maven → 11.0.21
- maven
<dependency><groupId>org.apache.tomcat</groupId><artifactId>tomcat</artifactId><version>11.0.21</version></dependency>- gradle
implementation("org.apache.tomcat:tomcat:11.0.21")
org.apache.tomcat:tomcat-tribes Maven → 11.0.21
- maven
<dependency><groupId>org.apache.tomcat</groupId><artifactId>tomcat-tribes</artifactId><version>11.0.21</version></dependency>- gradle
implementation("org.apache.tomcat:tomcat-tribes:11.0.21")
Severity breakdown
CVSS 3.1 7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Weakness
CWE-311: Missing Encryption of Sensitive Data
The product does not encrypt sensitive or critical information before storage or transmission.
How to prevent it
- Requirements: Clearly specify which data or resources are valuable enough that they should be protected by encryption. Require that any transmission or storage of this data/resource should use well-vetted encryption algorithms.
- Architecture and Design: Ensure that encryption is properly integrated into the system design, including but not necessarily limited to: Encryption that is needed to store or transmit private data of the users of the system Encryption that is needed to protect the system itself from unauthorized disclosure or tampering Identify the separate needs and contexts for encryption: One-way (i.e., only the user or recipient needs to have the key). This can be achieved using public key cryptography, or other techniques in which the encrypting party (i.e., the product) does not need to have access to a private key. Two-way (i.e., the encryption can be automatically performed on behalf of a user, but the key must be available so that the plaintext can be automatically recoverable by that user). This requires storage of the private key in a format that is recoverable only by the user (or perhaps by the operating system) in a way that cannot be recovered by others. Using threat modeling or other techniques, assume that data can be compromised through a separate vulnerability or weakness, and determine where encryption will be most effective. Ensure that data that should be private is not being inadvertently exposed using weaknesses such as insecure permissions (CWE-732). [REF-7]
- Architecture and Design: When there is a need to store or transmit sensitive data, use strong, up-to-date cryptographic algorithms to encrypt that data. Select a well-vetted algorithm that is currently considered to be strong by experts in the field, and use well-tested implementations. As with all cryptographic mechanisms, the source code should be available for analysis. For example, US government systems require FIPS 140-2 certification. Do not develop custom or private cryptographic algorithms. They will likely be exposed to attacks that are well-understood by cryptographers. Reverse engineering techniques are mature. If the algorithm can be compromised if attackers find out how it works, then it is especially weak. Periodically ensure that the cryptography has not become obsolete. Some older algorithms, once thought to require a billion years of computing time, can now be broken in days or hours. This includes MD4, MD5, SHA1, DES, and other algorithms that were once regarded as strong. [REF-267]
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
- Implementation, Architecture and Design: When using industry-approved techniques, use them correctly. Don't cut corners by skipping resource-intensive steps (CWE-325). These steps are often essential for preventing common attacks.
- Implementation: Use naming conventions and strong types to make it easier to spot when sensitive data is being used. When creating structures, objects, or other complex entities, separate the sensitive and non-sensitive data as much as possible.
References
Advisories
- github.com/advisories/GHSA-69r9-qgr7-g2wj
- nvd.nist.gov/vuln/detail/CVE-2026-34486
- access.redhat.com/errata/RHSA-2026:36787
- access.redhat.com/errata/RHSA-2026:36788
- access.redhat.com/errata/RHSA-2026:36789
- access.redhat.com/errata/RHSA-2026:36790
- access.redhat.com/errata/RHSA-2026:36876
- access.redhat.com/errata/RHSA-2026:36877
- access.redhat.com/errata/RHSA-2026:36878
- access.redhat.com/errata/RHSA-2026:36879
- access.redhat.com/errata/RHSA-2026:37136
- access.redhat.com/errata/RHSA-2026:37137
- access.redhat.com/errata/RHSA-2026:38505
- access.redhat.com/errata/RHSA-2026:39188
- access.redhat.com/errata/RHSA-2026:39189
- access.redhat.com/security/cve/CVE-2026-34486
- bugzilla.redhat.com/show_bug.cgi
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-34486.json
- socradar.io/blog/snowlight-government-chinese-campaign
Fixes and patches
Packages
Other links
- lists.apache.org/thread/9510k5p5zdvt9pkkgtyp85mvwxo2qrly
- tomcat.apache.org/security-10.html
- tomcat.apache.org/security-11.html
- tomcat.apache.org/security-9.html
- herodevs.com/vulnerability-directory/cve-2026-34486
- vicarius.io/vsociety/posts/cve-2026-34486-detection-script-rce-on-apache-tomcat
- vicarius.io/vsociety/posts/cve-2026-34486-mitigation-script-rce-on-apache-tomcat
- cisa.gov/known-exploited-vulnerabilities-catalog
Timeline
- Published
- Added to CISA's Known Exploited Vulnerabilities catalog
- Remediation due for U.S. federal agencies
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-h3x4-894j-xpx5 Apache Tomcat's FORM authentication process has an Incorrect Authorization vulnerability | Critical | Also affects org.apache.tomcat:tomcat |
| GHSA-9xv2-5v5q-p794 Apache Tomcat's DIGEST authenticator has an Authentication Bypass by Capture-replay vulnerability | Critical | Also affects org.apache.tomcat:tomcat |
| GHSA-gcx9-497g-6cp6 Apache Tomcat has an Improper Access Control, Incorrect Authorization vulnerability | Critical | Also affects org.apache.tomcat:tomcat |
| GHSA-5m62-pw8w-7w9f Apache Tomcat - Security constraints not correctly applied | Critical | Also affects org.apache.tomcat:tomcat |
| GHSA-9m89-8frq-c98c Apache Tomcat - AJP secret compared in non-constant time | Low | Also affects org.apache.tomcat:tomcat |
| GHSA-5mp6-jrq3-r938 Apache Tomcat: LockOutRealm treats user names as case-sensitive | High | Also affects org.apache.tomcat:tomcat |
| GHSA-h6fc-48rj-7qqh Apache Tomcat - Digest authenticator will authenticate any unknown user | Critical | Also affects org.apache.tomcat:tomcat |
| GHSA-fv25-8xcx-gqjc Apache Tomcat - WebSocket authentication header exposure | High | Also affects org.apache.tomcat:tomcat |
Credits: tkwilli94
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor