← Back
ROOT-APP-MAVEN-CVE-2025-66614

Vulnerability in io.root.org.apache.tomcat:tomcat-catalina (ROOT-APP-MAVEN-CVE-2025-66614)

Summary

vulnerability in io.root.org.apache.tomcat:tomcat-catalina (ROOT-APP-MAVEN-CVE-2025-66614). Confidential information can be exposed externally. Mitigation: upgrade to `11.0.6-root.io.2, 11.0.11-root.io.2, 11.0.7-root.io.2, 11.0.6-root.io.3, 11.0.10-root.io.2, 11.0.8-root.io.2, 11.0.6-root.io.4, 11.0.11-root.io.3, 10.1.39-root.io.2, 10.1.39-root.io.3, 10.1.39-root.io.4, 10.1.39-root.io.5, 10.1.39-root.io.6, 10.1.39-root.io.7, 10.1.39-root.io.8, 10.1.39-root.io.9, 10.1.39-root.io.10, 10.1.39-root.io.11, 10.1.39-root.io.12` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **ROOT-APP-MAVEN-CVE-2025-66614** has been found in io.root.org.apache.tomcat:tomcat-catalina. Confidential information can be exposed externally. CVSS score: ?/10. What to do: upgrade io.root.org.apache.tomcat:tomcat-catalina to **11.0.6-root.io.2, 11.0.11-root.io.2, 11.0.7-root.io.2, 11.0.6-root.io.3, 11.0.10-root.io.2, 11.0.8-root.io.2, 11.0.6-root.io.4, 11.0.11-root.io.3, 10.1.39-root.io.2, 10.1.39-root.io.3, 10.1.39-root.io.4, 10.1.39-root.io.5, 10.1.39-root.io.6, 10.1.39-root.io.7, 10.1.39-root.io.8, 10.1.39-root.io.9, 10.1.39-root.io.10, 10.1.39-root.io.11, 10.1.39-root.io.12** or later. If unsure, ask your IT team or search "io.root.org.apache.tomcat:tomcat-catalina ROOT-APP-MAVEN-CVE-2025-66614" on the vendor's site.
ROOT-APP-MAVEN-CVE-2025-66614 (io.root.org.apache.tomcat:tomcat-catalina) — Attack vector: remote (network-reachable) / unauthenticated / no user interaction Patched: `11.0.6-root.io.2, 11.0.11-root.io.2, 11.0.7-root.io.2, 11.0.6-root.io.3, 11.0.10-root.io.2, 11.0.8-root.io.2, 11.0.6-root.io.4, 11.0.11-root.io.3, 10.1.39-root.io.2, 10.1.39-root.io.3, 10.1.39-root.io.4, 10.1.39-root.io.5, 10.1.39-root.io.6, 10.1.39-root.io.7, 10.1.39-root.io.8, 10.1.39-root.io.9, 10.1.39-root.io.10, 10.1.39-root.io.11, 10.1.39-root.io.12` — 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** (unclassified) exists in io.root.org.apache.tomcat:tomcat-catalina.
📍 Affected scope
io.root.org.apache.tomcat:tomcat-catalina — .
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **11.0.6-root.io.2, 11.0.11-root.io.2, 11.0.7-root.io.2, 11.0.6-root.io.3, 11.0.10-root.io.2, 11.0.8-root.io.2, 11.0.6-root.io.4, 11.0.11-root.io.3, 10.1.39-root.io.2, 10.1.39-root.io.3, 10.1.39-root.io.4, 10.1.39-root.io.5, 10.1.39-root.io.6, 10.1.39-root.io.7, 10.1.39-root.io.8, 10.1.39-root.io.9, 10.1.39-root.io.10, 10.1.39-root.io.11, 10.1.39-root.io.12**.
🛡️ 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 'io.root.org.apache.tomcat:tomcat-catalina' .` 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

  1. 1
    Identify exposure identify
    grep -r 'io.root.org.apache.tomcat:tomcat-catalina' . | grep -v node_modules

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

  2. 6
    Apply patch patch
    Upgrade io.root.org.apache.tomcat:tomcat-catalina to 11.0.6-root.io.2, 11.0.11-root.io.2, 11.0.7-root.io.2, 11.0.6-root.io.3, 11.0.10-root.io.2, 11.0.8-root.io.2, 11.0.6-root.io.4, 11.0.11-root.io.3, 10.1.39-root.io.2, 10.1.39-root.io.3, 10.1.39-root.io.4, 10.1.39-root.io.5, 10.1.39-root.io.6, 10.1.39-root.io.7, 10.1.39-root.io.8, 10.1.39-root.io.9, 10.1.39-root.io.10, 10.1.39-root.io.11, 10.1.39-root.io.12

    ステージング環境で 11.0.6-root.io.2, 11.0.11-root.io.2, 11.0.7-root.io.2, 11.0.6-root.io.3, 11.0.10-root.io.2, 11.0.8-root.io.2, 11.0.6-root.io.4, 11.0.11-root.io.3, 10.1.39-root.io.2, 10.1.39-root.io.3, 10.1.39-root.io.4, 10.1.39-root.io.5, 10.1.39-root.io.6, 10.1.39-root.io.7, 10.1.39-root.io.8, 10.1.39-root.io.9, 10.1.39-root.io.10, 10.1.39-root.io.11, 10.1.39-root.io.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

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

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

Affected packages

Root:Maven io.root.org.apache.tomcat:tomcat-catalina
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"11.0.6-root.io.2"},{"fixed":"11.0.11-root.io.2"},{"fixed":"11.0.7-root.io.2"},{"fixed":"11.0.6-root.io.3"},{"fixed":"11.0.10-root.io.2"},{"fixed":"11.0.8-root.io.2"},{"fixed":"11.0.6-root.io.4"},{"fixed":"11.0.11-root.io.3"},{"fixed":"10.1.39-root.io.2"},{"fixed":"10.1.39-root.io.3"},{"fixed":"10.1.39-root.io.4"},{"fixed":"10.1.39-root.io.5"},{"fixed":"10.1.39-root.io.6"},{"fixed":"10.1.39-root.io.7"},{"fixed":"10.1.39-root.io.8"},{"fixed":"10.1.39-root.io.9"},{"fixed":"10.1.39-root.io.10"},{"fixed":"10.1.39-root.io.11"},{"fixed":"10.1.39-root.io.12"}]}]

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →