Path Traversal in org.springframework:spring-webmvc (CVE-2026-47884)
Summary
Path traversal in org.springframework:spring-webmvc (CVE-2026-47884). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 7.0.9 or later.
Original description
The description as published by the source.
Use of XsltView in a Spring MVC application can result in SSRF and RCE attack if the application has an "/**" mapping that results in view rendering, and where the view name is not explicitly specified.
Spring Framework 7.0.0 - 7.0.8
Spring Framework 6.2.0 - 6.2.19
Spring Framework 6.1.0 - 6.1.28
Spring Framework 6.0.0 - 6.0.30
Spring Framework 5.3.0 - 5.3.49
Spring Framework 5.2.25.RELEASE and earlier
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-47884 has been found in org.springframework:spring-webmvc.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade org.springframework:spring-webmvc to 7.0.9 or later.
If unsure, ask your IT team or search "org.springframework:spring-webmvc CVE-2026-47884" on the vendor's site.
CVE-2026-47884 (org.springframework:spring-webmvc) — CWE-22 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 7.0.9 — 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.
Path traversal (CWE-22) exists in org.springframework:spring-webmvc.
Check the vendor advisory for the affected versions of org.springframework:spring-webmvc.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 7.0.9.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.springframework:spring-webmvc を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.springframework:spring-webmvc to 7.0.9ステージング環境で 7.0.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web nvd.nist.gov
- web spring.io
- web github.com
- web github.com