Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-55957 high CVSS 7.3

Vulnerability in tomcat (CVE-2026-55957)

Summary

Vulnerability in tomcat (CVE-2026-55957). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 9.0.101, 10.1.37, 11.0.5 or later.

Original description

The description as published by the source.

Missing Critical Step in Authentication vulnerability in Apache Tomcat when the JNDIRealm was configured to authenticate binds using GSSAPI allowed attackers to authenticate without provided the correct password.

This issue affects Apache Tomcat: from 11.0.0 through 11.0.4, from 10.1.0 through 10.1.36, from 9.0.0 through 9.0.100, from 8.5.0 through 8.5.100, from 7.0.0 through 7.0.109.

Users are recommended to upgrade to version 11.0.5, 10.1.37 or 9.0.101, 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-55957 has been found in tomcat.
Risk of unauthorized operations or information disclosure. CVSS score: 7.3/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-55957" on the vendor's site.

CVE-2026-55957 (tomcat) — CWE-304 / CVSS v3 7.3
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.

❓ What is the problem

A vulnerability (CWE-304) exists in tomcat.

📍 Affected scope

Check the vendor advisory for the affected versions of tomcat.

🔥 Severity

Severity: High (CVSS 7.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 9.0.101, 10.1.37, 11.0.5.

🛡️ 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
    Apply patch patch 
    Upgrade tomcat to 9.0.101, 10.1.37, 11.0.5

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

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

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

Affected packages

Bitnami tomcat
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"9.0.101"},{"introduced":"10.0.0"},{"fixed":"10.1.37"},{"introduced":"11.0.0"},{"fixed":"11.0.5"}]}]

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