CVE-2026-95517

Information Exposure
Affects
Apache Tomcat
in
Apache Tomcat
No items found.
Versions
>=7.0.100 <=7.0.109, >=8.5.38 <=8.5.100, >=9.0.13 <=9.0.123, >=10.1.0-M1 <=10.1.61, >=11.0.0-M1 <=11.0.27

Patch Available.

Exclamation circle icon
Patch Available

This Vulnerability has been fixed in the Never-Ending Support (NES) version offered by HeroDevs.

Overview

Apache Tomcat is an open-source implementation of the Jakarta Servlet, Jakarta Pages, Jakarta Expression Language, Jakarta WebSocket, Jakarta Annotations, and Jakarta Authentication specifications. It serves Java web applications either as a standalone servlet container and HTTP server or embedded inside an application through the tomcat-embed-core artifact. Its Catalina servlet container (org.apache.tomcat:tomcat-catalina) supplies the request-processing pipeline, including Valves such as RewriteValve, along with connectors, realms, and session management.

An information exposure vulnerability (CVE-2026-95517) has been identified in the EncryptInterceptor of the Apache Tomcat cluster communication library (Tribes), which allows attackers with access to the cluster network to alter encrypted cluster messages without detection and to observe cluster data that the interceptor sends unencrypted. The interceptor relies on encryption of security-relevant cluster messages without checking their integrity, and it does not protect all of the data it transmits.

Per OWASP: Access control enforces policy such that users cannot act outside of their intended permissions. Failures typically lead to unauthorized information disclosure, modification, or destruction of all data or performing a business function outside the user's limits.

This issue affects multiple versions of Apache Tomcat.

Details

Module Info

Vulnerability Info

This Medium-severity vulnerability is found in the org.apache.tomcat:tomcat-tribes package in multiple versions of Apache Tomcat. The EncryptInterceptor (org.apache.catalina.tribes.group.interceptors.EncryptInterceptor) is an optional channel interceptor that encrypts the messages Tomcat cluster members exchange, such as replicated session data, using a pre-shared key. Its default cipher is AES in CBC mode with PKCS5 padding, and the interceptor adds no message authentication code or other integrity check:

private static final String DEFAULT_ENCRYPTION_ALGORITHM = "AES/CBC/PKCS5Padding";

On send, sendMessage() encrypts only the payload bytes of the channel message and replaces them with a random IV followed by the ciphertext. On receipt, messageReceived() decrypts whatever arrives and hands the result straight to the next interceptor in the channel stack:

public void messageReceived(ChannelMessage msg) {
    try {
        byte[] data = msg.getMessage().getBytes();

        data = encryptionManager.decrypt(data);

        XByteBuffer xbb = msg.getMessage();

        // Completely replace the message with the decrypted one
        xbb.clear();
        xbb.append(data, 0, data.length);

        super.messageReceived(msg);
    } catch (GeneralSecurityException gse) {
        log.error(sm.getString("encryptInterceptor.decrypt.failed"), gse);
    }
}

decrypt() only splits off the IV and calls Cipher.doFinal() on the remainder. CBC decryption does not detect modification: flipping bits in the IV or in a ciphertext block changes the decrypted plaintext in a predictable way, and the only check applied is the padding check. A modified message that still has valid padding is therefore accepted as genuine and passed on for deserialization and processing as cluster data, so an attacker who can intercept or inject traffic on the cluster network can alter cluster messages without holding the key. The interceptor can be configured with other cipher modes, such as GCM, but unless an administrator changes encryptionAlgorithm, every cluster message uses this unauthenticated CBC mode. In addition, the interceptor encrypts only the message payload, so the rest of each channel message, such as the sending member, message identifier, timestamp and options, still crosses the network in clear text.

Mitigation

Only recent versions of Apache Tomcat are community-supported. The community support version will not receive any updates to address this issue. For more information, see here.

Users of the affected components should apply one of the following mitigations:

  • Upgrade to a patched version of Apache Tomcat.
  • Leverage a commercial support partner like HeroDevs for post-EOL security support.

Credits

Vulnerability Details
Severity
Level
CVSS Assessment
Low
>=0 <4
Medium
>=4 <6
High
>=6 <8
Critical
>=8 <10
Medium
ID
CVE-2026-95517
PROJECT Affected
Apache Tomcat
Versions Affected
>=7.0.100 <=7.0.109, >=8.5.38 <=8.5.100, >=9.0.13 <=9.0.123, >=10.1.0-M1 <=10.1.61, >=11.0.0-M1 <=11.0.27
NES Versions Affected
Published date
November 20, 2026
≈ Fix date
Category
Information Exposure
Vex Document
Download VEXHow do I use it?
Sign up for the latest vulnerability alerts fixed in
NES for Apache Tomcat
Rss feed icon
Subscribe via RSS
or

By submitting the form I acknowledge receipt of our Privacy Policy.

Thanks for signing up for our Newsletter! We look forward to connecting with you.
Oops! Something went wrong while submitting the form.