← Back
CVE-2026-40973
high
CVSS 7.0
Vulnerability in org.springframework.boot:spring-boot (CVE-2026-40973)
Summary
vulnerability in org.springframework.boot:spring-boot (CVE-2026-40973). Successful exploitation can lead to full system takeover. Exploitable via ``ApplicationTemp``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-40973** has been found in org.springframework.boot:spring-boot.
Attackers can target a specific entry point like ``ApplicationTemp`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.0/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "org.springframework.boot:spring-boot CVE-2026-40973" on the vendor's site.
CVE-2026-40973 (org.springframework.boot:spring-boot) — CWE-377 / CVSS v3 7.0
Attack vector: local / no user interaction
Attack surface: `ApplicationTemp` / `server.servlet.session.persistent` / `true`
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-377) exists in org.springframework.boot:spring-boot. Attackers reach the vulnerable code path via ``ApplicationTemp`` without authentication.
📍 Affected scope
org.springframework.boot:spring-boot — . Attack surface: `ApplicationTemp` / `server.servlet.session.persistent` / `true`.
🔥 Severity
Severity: High (CVSS 7.0/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ 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.springframework.boot:spring-boot' .` 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.springframework.boot:spring-boot' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.springframework.boot:spring-boot` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Maven
org.springframework.boot:spring-boot
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"2.7.32"}]}]