Vulnerability in tomcat (CVE-2026-53434)
Summary
Vulnerability in tomcat (CVE-2026-53434). Confidential information can be exposed externally. Mitigation: upgrade to 9.0.101, 10.1.37, 11.0.5 or later.
Original description
The description as published by the source.
Detection of Error Condition Without Action vulnerability in Apache Tomcat when configuring CRLs for a FFM based connector.
This issue affects Apache Tomcat: from 11.0.0 through 11.0.22, from 10.1.0 through 10.1.55, from 9.0.83 through 9.0.118.
Users are recommended to upgrade to version 11.0.23, 10.1.56 or 9.0.119, which fixes the issue.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-53434 has been found in tomcat.
Confidential information can be exposed externally. CVSS score: 9.1/10.
What to do: upgrade tomcat to 9.0.101, 10.1.37, 11.0.5 or later.
If unsure, ask your IT team or search "tomcat CVE-2026-53434" on the vendor's site.
CVE-2026-53434 (tomcat) — CWE-390 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 9.0.101, 10.1.37, 11.0.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-390) exists in tomcat.
Check the vendor advisory for the affected versions of tomcat.
Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally.
Update to 9.0.101, 10.1.37, 11.0.5.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'tomcat' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'tomcat' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
tomcatを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade tomcat to 9.0.101, 10.1.37, 11.0.5ステージング環境で 9.0.101, 10.1.37, 11.0.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-53434 tomcat10
- Ubuntu UBUNTU-CVE-2026-53434 tomcat6
References
- advisory lists.apache.org
- advisory openwall.com
- ATLASSIAN JSWSERVER-26932
- web nvd.nist.gov
- web github.com