Skip to content
Reachability Analysis

CVE-2026-34486: Apache Software Foundation Apache Tomcat, exploitable where you run it

Code called: openReached: yesControl in front: noExploitation known: yesWalk it through the four questions

What the flaw is

Tomcat can replicate user sessions between nodes over a cluster channel. The EncryptInterceptor is the component that encrypts those channel messages. CVE-2026-29146 covered a padding oracle weakness in its default cipher mode (CBC). The fix for it shipped in Tomcat 11.0.20, 10.1.53 and 9.0.116, and that fix contained an error, and CVE-2026-34486 is that error: it allows the EncryptInterceptor to be bypassed, so data on the channel is not protected as intended (CWE-311, missing encryption of sensitive data). Apache's own severity rating for it is Important; the CVSS base score is separate (next paragraph).

The CVSS 3.1 base score is 7.5, with high impact on confidentiality only. The practical risk is larger than that CVSS score suggests. SOCRadar reports that attackers used a public Java deserialization toolkit against the cluster port of Tomcat 9.0.116 servers and ran commands on them, which means that a bypassed channel can carry attacker-supplied serialized data into the node. CISA's KEV entry adds that the flaw can be chained with CVE-2025-24813, a Tomcat flaw in partial PUT handling of the default servlet that can allow code execution when its own conditions hold.

Only three exact releases are affected, so most Tomcat servers are not exposed to this CVE. Servers that do not use clustering, or use it without the EncryptInterceptor, are outside the flaw.

Are you exposed: each condition and how to check it

Condition for exposureHow to check it on your system
Version: the node runs Tomcat 11.0.20, 10.1.53 or 9.0.116.Run version.sh (Linux) or version.bat (Windows) in the Tomcat bin directory, or catalina.sh version. Read the Server number line. On a package install run rpm -q tomcat or dpkg -l | grep tomcat and compare with the distribution errata, since backported builds keep older version numbers.
The Cluster channel in server.xml uses the EncryptInterceptor, and its receiver port (default 4000) is reachable from hosts outside the cluster.grep -n -e 'Cluster' -e 'EncryptInterceptor' $CATALINA_BASE/conf/server.xml. Both must appear outside XML comments, with the Interceptor element (class org.apache.catalina.tribes.group.interceptors.EncryptInterceptor) inside the Channel element. Then find the Receiver element (class org.apache.catalina.tribes.transport.nio.NioReceiver, default port 4000, autoBind 100, so any port from 4000 to 4100). On the host run ss -ltnp | grep java and look for those ports. From a host outside the cluster run nc -vz 4000, and review iptables -S, nft list ruleset or firewall-cmd --list-all and the network ACL or security group for rules on the port range. The condition holds if the outside host connects.
Only for the chain CISA mentions: the conditions of CVE-2025-24813 also hold. These are, per the Tomcat security page, writes enabled for the default servlet (off by default), partial PUT support (on by default), file-based session persistence at its default location, and a library on the class path that can be abused through deserialization.In conf/web.xml look at the default servlet init-param readonly (a value of false enables writes). In conf/context.xml or the web app, look for a PersistentManager with FileStore. Check the Tomcat version against the CVE-2025-24813 fix (11.0.3, 10.1.35 and 9.0.99, per the Tomcat security pages).

Affected and fixed versions

Scroll the table sideways for more columns

Apache lists no other release as affected. Earlier releases of each branch carry the older CVE-2026-29146 flaw instead, which Apache lists as a separate issue. Apache announced the CVE on 9 Apr 2026, after all three fixed releases were out. Distributions such as RHEL backport fixes under their own package versions, so check the distribution errata for packaged installs.
Tomcat branchAffected versionFirst fixed versionFix released (per Tomcat changelog)
11.0.x11.0.20 only11.0.214 Apr 2026
10.1.x10.1.53 only10.1.542 Apr 2026
9.0.x9.0.116 only9.0.1173 Apr 2026

If the fix cannot go in yet

  • Upgrade to Tomcat 11.0.21, 10.1.54 or 9.0.117 or later. This is the vendor fix. It needs a restart of each node, so plan a rolling restart if sessions are replicated. Apache lists no workaround.
  • Limit the cluster receiver port to the other cluster nodes with a host firewall or network ACL. The Tomcat clustering guide says clusters are meant for a trusted network. Cost: any host that is not a cluster member loses access to that port, and a node added to the cluster later needs a new rule.
  • Where a trusted network is not available, the Tomcat 11 clustering guide describes a TLS-protected channel (secure attribute on the Channel, pre-shared key and identity, securePort on the Receiver). Cost: it needs OpenSSL-FFM on Java 22 or later, or Tomcat Native 1.2.17 or later, and the same settings on every node. The Tomcat 11 configuration reference also marks the EncryptInterceptor as deprecated and says it should no longer be used to secure cluster traffic.
  • Red Hat states that no mitigation meeting its criteria exists for its Tomcat packages, so RHEL and JBoss Web Server users take the vendor errata.

What to look for

  • SOCRadar indicators for the campaign that used this CVE: attacker hosts 130[.]94[.]17[.]180 and 130[.]94[.]30[.]168 (payload served from port 8080 path /slt), secondary host 92[.]38[.]135[.]196 on port 8888, and 149[.]129[.]37[.]105 on port 30005. Also look for outbound curl or wget from the Tomcat process piped to sh, a file at /tmp/log_de.log, a process that names itself [kworker/0:2], and memfd_create with fexecve in EDR telemetry. SOCRadar also lists /error.jsp and /tunnel.jsp web shells, but those belong to the CVE-2025-24813 part of the campaign.
  • Unexpected child processes of the Tomcat Java process (shells, curl, wget) and connections to the cluster port from hosts outside the cluster are the generic signs of exploitation of this class of flaw.

Exploited 15 days after disclosure: disclosed 9 Apr 2026, first exploitation reported 24 Apr 2026.

Exploitation reported so far

SOCRadar published a report on 31 Jul 2026 about a China-nexus campaign it calls SNOWLIGHT. Its timeline lists exploitation of CVE-2026-34486 against Taiwanese Tomcat hosts as "~Apr 24-29" 2026 (a range, so 24 Apr is the earliest date it gives), and exploitation of CVE-2025-24813 on 8 May 2026. SOCRadar's recovered command history shows a public Java deserialization toolkit pointed at Tomcat 9.0.116 on port 4000, delivering a download-and-run shell command that installs the SNOWLIGHT malware. SOCRadar's target table lists 98 raw entries and 37 unique hosts for this CVE, with 2 confirmed compromises by live command execution.

CISA added the CVE to KEV on 4 Aug 2026, four days after the report. KEV lists ransomware campaign use as Unknown. SOCRadar describes the Tomcat flaws as separate exploitation runs, and neither Apache nor CISA publishes the steps of the chain with CVE-2025-24813.

Why static reachability settles it

Exposure needs three things at once: one of three exact Tomcat builds, an EncryptInterceptor in the cluster channel, and network reach to the receiver port. Inspecting the version, server.xml and listening sockets answers all three on a given node, so static reachability settles it. KEV and SOCRadar show real attacks, which raises the priority for any node that passes all three checks. See static reachability for what the method proves and misses.

Sources

  1. CVE-2026-34486: NVD record, read 19 Nov 2026
  2. CVE-2026-34486: CISA KEV entry (feed version 2026.11.18), read 19 Nov 2026
  3. CVE-2026-34486: Apache Tomcat security announcement (vendor advisory, 9 Apr 2026), read 19 Nov 2026
  4. CVE-2026-34486: Apache Tomcat 11 security page (vendor advisory, per-branch details, report dates), read 19 Nov 2026
  5. CVE-2026-34486: Apache Tomcat 10 security page (vendor advisory), read 19 Nov 2026
  6. CVE-2026-34486: Apache Tomcat 9 security page (vendor advisory), read 19 Nov 2026
  7. CVE-2026-34486: Tomcat 11 changelog (release dates), read 19 Nov 2026
  8. CVE-2026-34486: Tomcat 10.1 changelog (release dates), read 19 Nov 2026
  9. CVE-2026-34486: Tomcat 9 changelog (release dates), read 19 Nov 2026
  10. CVE-2026-34486: Tomcat 11 cluster interceptor reference, read 19 Nov 2026
  11. CVE-2026-34486: Tomcat 11 clustering guide, read 19 Nov 2026
  12. CVE-2026-34486: SOCRadar research on the SNOWLIGHT campaign (exploitation and indicators), read 19 Nov 2026
  13. CVE-2026-34486: Red Hat CVE page, read 19 Nov 2026

Last reviewed 19 Nov 2026.