Skip to content
Fencer Intel
medium —

CVE-2026-95517 json

Apache Tomcat: Multiple vulnerabilities in EncryptInterceptor

published 3h ago modified 2h ago also EUVD-2026-130760

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

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

Is CVE-2026-95517 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-95517 updated cvss 7.4

tomcat: tomcat: Information disclosure via improper cryptographic validation in EncryptInterceptor

  • Red Hat Hardened Images tomcat10 10.1.61-0.1.hum1, tomcat11 11.0.27-0.1.hum1
    affected: workaround, no fix available

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Affected products

  • Apache Software Foundation Apache Tomcat

Classification

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
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.