Small business IT admins: if you run Apache Tomcat, a recently disclosed vulnerability in its encryption component is being actively exploited in the wild. CISA has warned about CVE-2026-34486, and security researchers have observed active attacks against vulnerable deployments. Patch this week to close the door on attackers.
What happened
The vulnerability, CVE-2026-34486, is described as an encryption-related flaw in Apache Tomcat that could allow attackers to bypass EncryptInterceptor in clustered deployments. The flaw has been observed in active attacks, making it important to patch quickly according to advisories from CISA and researchers such as Unit 42.
Why it matters
Why readers should care: If you rely on Tomcat to host apps or API endpoints, an attacker could intercept or tamper traffic or exfiltrate data if exploited. The vulnerability is especially risky for teams with publicly exposed Tomcat clusters. Patching reduces the window of exposure and helps protect customer data and uptime.
Practical steps you can take now
- Step 1 — Identify your Tomcat version: Run a quick check to see which Tomcat version you’re running. On Linux, you can run: ps -ef | grep [t]omcat and then run catalina.sh version from the Tomcat bin directory. If you’re using a packaged distro, check the package manager (for example, apt-cache policy tomcat9 or yum list tomcat).
- Step 2 — Verify advisory and patch availability: Visit the official Apache Tomcat security bulletin for CVE-2026-34486 and confirm a patched release exists for your series (8.x/9.x/10.x). Read the bulletin to understand any configuration changes recommended by Apache.
- Step 3 — Patch your Tomcat: Plan a quick maintenance window. Back up server config, stop Tomcat, replace the binaries with the patched release, and restart. Example steps (adjust paths to your environment):
– systemctl stop tomcat
– cd /opt/tomcat
– download patched release tar.gz from Apache
– tar -xzf apache-tomcat-*.tar.gz -C /opt/tomcat –strip-components=1
– systemctl start tomcat
After patch, verify TLS configuration by checking a test endpoint with openssl s_client -connect your-host:443 and ensure no TLS errors show up. - Step 4 — Harden and monitor: Ensure TLS is enabled, enforce strong ciphers, monitor access logs for unusual patterns, and enable alerts for failed TLS handshakes or unusual POST requests to your endpoints.
- Step 5 — Plan for regular patching: If you haven’t already, set up automated patching for your Java servers and include Tomcat in your vulnerability management workflow. Review official advisories weekly to stay informed.
Final thought
Zero-days and actively exploited flaws are reminders to keep software patching at the top of your to-do list. Patching Tomcat this week reduces risk for your web apps and customers—two practical steps you can take today.
