← Back
CVE-2026-29145
Authentication Bypass in org.apache.tomcat:tomcat (CVE-2026-29145)
Summary
authentication bypass in org.apache.tomcat:tomcat (CVE-2026-29145). Confidential information can be exposed externally. Mitigation: upgrade to `11.0.20` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-29145** has been found in org.apache.tomcat:tomcat.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade org.apache.tomcat:tomcat to **11.0.20** or later.
If unsure, ask your IT team or search "org.apache.tomcat:tomcat CVE-2026-29145" on the vendor's site.
CVE-2026-29145 (org.apache.tomcat:tomcat) — CWE-287 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `11.0.20` — 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.
❓ What is the problem
**authentication bypass** (CWE-287) exists in org.apache.tomcat:tomcat.
📍 Affected scope
org.apache.tomcat:tomcat — .
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **11.0.20**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'org.apache.tomcat:tomcat' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'org.apache.tomcat:tomcat' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.apache.tomcat:tomcat` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade org.apache.tomcat:tomcat to 11.0.20ステージング環境で 11.0.20 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
org.apache.tomcat:tomcat
[{"type":"ECOSYSTEM","events":[{"introduced":"11.0.0-M1"},{"fixed":"11.0.20"}]}]
maven
org.apache.tomcat:tomcat-coyote-ffm
[{"type":"ECOSYSTEM","events":[{"introduced":"11.0.0-M1"},{"fixed":"11.0.20"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-29145
- package https://github.com/apache/tomcat
- web https://lists.apache.org/thread/yz5fxmhd2j43wgqykssdo7kltws57jfz
- web http://www.openwall.com/lists/oss-security/2026/04/09/23
- web https://github.com/apache/tomcat/commit/721591f7bff424c693f26adc18ae9b9abac3655b
- web https://github.com/apache/tomcat/commit/d1406df5ae0326f39f54c3f64ac30d8fca55cd5b
- web https://github.com/apache/tomcat/commit/fe26667cd2385045ac73f4dea086cc9971209b90
- web https://tomcat.apache.org/security-10.html#Fixed_in_Apache_Tomcat_10.1.53
- web https://tomcat.apache.org/security-11.html#Fixed_in_Apache_Tomcat_11.0.20
- web https://tomcat.apache.org/security-9.html#Fixed_in_Apache_Tomcat_9.0.116
- web https://github.com/advisories/GHSA-95jq-rwvf-vjx4