CVE-2026-95517: Apache Tomcat: Multiple vulnerabilities in EncryptInterceptor
CVE-2026-95517 key facts
- CISA KEV
- Not listed (catalogue checked )
- Highest advisory rating
- High
- CVSS base score
- 7.4 (Red Hat)
- Weakness
- CWE-649 Reliance on obfuscation or encryption of Security-Relevant inputs without integrity checking
- CWE-354 Improper validation of integrity check value
- CWE-319 Cleartext transmission of sensitive information
- Fixed releases
- Apache: 11.0.29, 10.1.62, 9.0.124
- Assigned by
- apache (CNA)
- CVE record published
- Listed by VulniPulse
- Record changed
Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-95517; each belongs to its advisory, not to every product listed. How records are collected and checked.
Description
Reliance on obfuscation or encryption of Security-Relevant inputs without integrity checking, Improper validation of integrity check value, Cleartext transmission of sensitive information vulnerability in the EncryptInterceptor of Apache Tomcat. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.27, from 10.1.0-M1 through 10.1.61, from 9.0.13 through 9.0.123. The following versions were EOL at the time the CVE was created but are known to be affected: from 8.5.38 through 8.5.100, from 7.0.100 through 7.0.109. Other unsupported versions may also be affected. Users are recommended to upgrade to version 11.0.29, 10.1.62 or 9.0.124 and switch to TLS-PSK to encrypt cluster communication, which fixes the issue. Note: Tomcat 11.0.28 was not released
Text from the CVE.org record (apache).
How do I fix CVE-2026-95517?
Upgrade to a fixed release named by the vendor:
- Apache: 11.0.29, 10.1.62, 9.0.124
- Users are recommended to upgrade to version 11.0.29, 10.1.62 or 9.0.124 and switch to TLS-PSK to encrypt cluster communication, which fixes the issue. (Apache)
- Isolate cluster communication to trusted private networks, or restrict Tomcat cluster ports using host firewall rules so that communication is accepted solely from authorized cluster member nodes. 1. Restrict cluster ports (for example, TCP port 4000 configured in the Receiver element of server.xml) using firewalld: firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address=" " port port="4000" protocol="tcp" accept' firewall-cmd --reload 2. Alternatively, encapsulate cluster communication within an IPsec or VPN tunnel between cluster nodes to provide end-to-end transport layer encryption and integrity verification. Caveats: Limiting network reachability or tunneling cluster traffic requires network-level access and correct topology planning across all nodes. Reloading firewall rules or altering Tomcat's server.xml configuration requires restarting the Tomcat service, which causes a temporary interruption of application availability. (Red Hat)
Vendor advisories for CVE-2026-95517
Apache
1 advisory- Advisory severityMedium
Medium [CVE-2026-95517] Reliance on obfuscation or encryption of Security-Relevant inputs without integrity checking, Improper validation of integrity check value, Cleartext transmission of sensitive information vulnerability in the EncryptInterceptor of Apache Tomcat
CVE-2026-95517Source published Source updated
Reliance on obfuscation or encryption of Security-Relevant inputs without integrity checking, Improper validation of integrity check value, Cleartext transmission of sensitive information vulnerability in the EncryptInterceptor of Apache Tomcat. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.27, from 10.1.0-M1 through 10.1.61, from 9.0.13 through 9.0.123. The following versions were EOL at the time the CVE was created but are known to be affected: from 8.5.38 through 8.5.100, from 7.0.100 through 7.0.109. Other unsupported versions may also be affected. Users are recommended to upgrade to version 11.0.29, 10.1.62 or 9.0.124 and switch to TLS-PSK to encrypt cluster communication, which fixes the issue. Note: Tomcat 11.0.28 was not released
- Affected products in this advisory
- Apache Tomcat
- Source-reported affected versions
- 11.0.0-M1 through 11.0.27
- 10.1.0-M1 through 10.1.61
- 9.0.13 through 9.0.123.
- 8.5.38 through 8.5.100
3 more entries in the full advisory.
- Source-reported fixed versions
- 11.0.29
- 10.1.62
- 9.0.124
- Mitigation guidance
- Users are recommended to upgrade to version 11.0.29, 10.1.62 or 9.0.124 and switch to TLS-PSK to encrypt cluster communication, which fixes the issue.
Red Hat
1 advisory- Advisory severityHigh7.4
High [CVE-2026-95517] Information disclosure via improper cryptographic validation in EncryptInterceptor
CVE-2026-95517Source published Source updated
Information disclosure via improper cryptographic validation in EncryptInterceptor. Red Hat rates this important (CVSS 7.4). Weakness: CWE-354. Affected product named by the advisory: Red Hat Hardened Images.
- Related products — impact not confirmed
- Red Hat Hardened Images
- Source-reported affected versions
- Affected-version details not available in this record.
- Source-reported fixed versions
- No fixed-version detail extracted. This does not mean no fix exists.
- Mitigation guidance
- Isolate cluster communication to trusted private networks, or restrict Tomcat cluster ports using host firewall rules so that communication is accepted solely from authorized cluster member nodes. 1. Restrict cluster ports (for example, TCP port 4000 configured in the Receiver element of server.xml) using firewalld: firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="<PEER_NODE_IP>" port port="4000" protocol="tcp" accept' firewall-cmd --reload 2. Alternatively, encapsulate cluster communication within an IPsec or VPN tunnel between cluster nodes to provide end-to-end transport layer encryption and integrity verification. Caveats: Limiting network reachability or tunneling cluster traffic requires network-level access and correct topology planning across all nodes. Reloading firewall rules or altering Tomcat's server.xml configuration requires restarting the Tomcat service, which causes a temporary interruption of application availability.
References
Timeline
- CVE record published
- First vendor advisory listed by VulniPulse
More Apache advisories
CVE-2026-121649Nov 19, 2026Apache Tomcat information disclosureCVE-2026-133325Nov 19, 2026Key exchange without entity authentication vulnerability in Apache TomcatCVE-2026-118436Nov 19, 2026Apache Tomcat denial of serviceCVE-2026-118233Nov 19, 2026Apache Tomcat denial of serviceCVE-2026-118028Nov 19, 2026Execution After Redirect (EAR) vulnerability in Apache Tomcat in RedirectValveCVE-2026-117517Nov 19, 2026Apache Tomcat: The fix for CVE-2026-25854 was incomplete
Get an email when Apache publishes the next one.
See Apache's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.