← Back
CVE-2025-66614
Vulnerability in org.apache.tomcat.embed:tomcat-embed-core (CVE-2025-66614)
Summary
vulnerability in org.apache.tomcat.embed:tomcat-embed-core (CVE-2025-66614). Confidential information can be exposed externally. Exploitable via `Host header`. Mitigation: upgrade to `9.0.113` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-66614** has been found in org.apache.tomcat.embed:tomcat-embed-core.
Attackers can target a specific entry point like `Host header` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade org.apache.tomcat.embed:tomcat-embed-core to **9.0.113** or later.
If unsure, ask your IT team or search "org.apache.tomcat.embed:tomcat-embed-core CVE-2025-66614" on the vendor's site.
CVE-2025-66614 (org.apache.tomcat.embed:tomcat-embed-core) — CWE-20 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Host header
Patched: `9.0.113` — 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-20) exists in org.apache.tomcat.embed:tomcat-embed-core. Attackers reach the vulnerable code path via `Host header` without authentication.
📍 Affected scope
org.apache.tomcat.embed:tomcat-embed-core — . Attack surface: Host header.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **9.0.113**.
🛡️ 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.embed:tomcat-embed-core' .` 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.embed:tomcat-embed-core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.apache.tomcat.embed:tomcat-embed-core` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade org.apache.tomcat.embed:tomcat-embed-core to 9.0.113ステージング環境で 9.0.113 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
org.apache.tomcat.embed:tomcat-embed-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
maven
org.apache.tomcat:tomcat
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
maven
org.apache.tomcat:tomcat-coyote
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
References
- package https://github.com/apache/tomcat
- web https://nvd.nist.gov/vuln/detail/CVE-2025-66614
- web https://lists.apache.org/thread/vw6lxtlh2qbqwpb61wd3sv1flm2nttw7
- web https://github.com/apache/tomcat/commit/152c14885d45f5e0a8b59bd9f93c289cfe20ce30
- web https://github.com/apache/tomcat/commit/258a591b61f8cf5c22109e21e5a2a38b63454fd2
- web https://github.com/apache/tomcat/commit/5053fa82a1b2b52756810601227984a8b71888a4
- web https://github.com/apache/tomcat/commit/9276b5e783c8cd5b3fe2bb716306b65004bdd940
- web https://github.com/apache/tomcat/commit/972f9a5e2a07674d92610c478aac1b205d60724e
- web https://github.com/apache/tomcat/commit/a4aa74232e826028cd2f7ba0445caf8a8b52c509
- web https://tomcat.apache.org/security-10.html
- web https://tomcat.apache.org/security-11.html
- web https://tomcat.apache.org/security-9.html
- web https://github.com/advisories/GHSA-fpj8-gq4v-p354