Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-34486 CISA KEV high CVSS 7.5

[KEV] Vulnerability in Apache Tomcat (CVE-2026-34486)

Summary

Vulnerability in Apache Tomcat (CVE-2026-34486). Confidential information can be exposed externally. Listed in CISA KEV — actively exploited. Mitigation: upgrade to 9.0.117, 10.1.54, 11.0.21 or later.

Original description

The description as published by the source.

Missing Encryption of Sensitive Data vulnerability in Apache Tomcat due to the fix for CVE-2026-29146 allowing the bypass of the EncryptInterceptor.

This issue affects Apache Tomcat: 11.0.20, 10.1.53, 9.0.116.

Users are recommended to upgrade to version 11.0.21, 10.1.54 or 9.0.117, which fix the issue.

Source: NIST National Vulnerability Database NVD GitHub Advisory CISA KEV

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-34486 has been found in Apache Tomcat.
Confidential information can be exposed externally. CVSS score: 7.5/10.
Note: CISA has officially confirmed this is actively exploited in the wild. Treat it with elevated urgency.
What to do: upgrade Apache Tomcat to 9.0.117, 10.1.54, 11.0.21 or later.
If unsure, ask your IT team or search "Apache Tomcat CVE-2026-34486" on the vendor's site.

CVE-2026-34486 (Apache Tomcat) — CWE-311 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 9.0.117, 10.1.54, 11.0.21 — apply immediately
Listed in CISA KEV — actively exploited, treat as top priority.
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

A vulnerability (CWE-311) exists in Apache Tomcat.

📍 Affected scope

Check the vendor advisory for the affected versions of Apache Tomcat.

🔥 Severity

Severity: High (CVSS 7.5/10). Confidential information can be exposed externally. Listed in CISA KEV — actively exploited in the wild, treat as top priority.

🔧 How to fix

Update to 9.0.117, 10.1.54, 11.0.21.

🛡️ 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 '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

  1. 1
    Identify exposure identify 
    grep -r 'tomcat' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で tomcat を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Consider incident declaration escalate 
    Notify SOC / on-call

    CISA KEV登録済 = 実環境で悪用が観測されている。侵入の兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。

  3. 3
    Apply patch patch 
    Upgrade Apache Tomcat to 9.0.117, 10.1.54, 11.0.21

    ステージング環境で 9.0.117, 10.1.54, 11.0.21 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Bitnami tomcat
[{"type":"SEMVER","events":[{"introduced":"9.0.116"},{"fixed":"9.0.117"},{"introduced":"10.1.53"},{"fixed":"10.1.54"},{"introduced":"11.0.20"},{"fixed":"11.0.21"}]}]
maven org.apache.tomcat:tomcat
[{"type":"ECOSYSTEM","events":[{"introduced":"9.0.116"},{"fixed":"9.0.117"}]}]
maven org.apache.tomcat:tomcat-tribes
[{"type":"ECOSYSTEM","events":[{"introduced":"9.0.116"},{"fixed":"9.0.117"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details