Quick answers
- Is CVE-2026-47884 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47884 being exploited in the wild.
- How severe is CVE-2026-47884?
- Critical severity, with a CVSS score of 9.8, published 27 August 2026.
- Which products and versions are affected?
- org.springframework:spring-webmvc (Maven) ECOSYSTEM:introduced=0,last_affected=5.2.25.RELEASE.
- Is there a fix for CVE-2026-47884?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-47884 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-47884?
- Check whether you run org.springframework:spring-webmvc (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This vulnerability exists in Spring Framework's XsltView when applications configure a "/**" path mapping that results in automatic view rendering without explicit view name specification. The vulnerable component fails to properly validate or sanitize user-controlled view names, enabling both SSRF attacks (allowing the attacker to make requests to arbitrary internal or external URLs) and RCE through malicious XSLT stylesheets. The attack is network-accessible and does not require authentication. Affected versions include Spring Framework 5.2.25.RELEASE and earlier, 5.3.0–5.3.49, 6.0.0–6.0.30, 6.1.0–6.1.28, 6.2.0–6.2.19, and 7.0.0–7.0.8. Patches are available in patched versions outside these ranges.
Affected products
- Spring Spring Framework 5.2.25.RELEASE and earlier, 5.3.0–5.3.49, 6.0.0–6.0.30, 6.1.0–6.1.28, 6.2.0–6.2.19, 7.0.0–7.0.8
Identifiers
- CVE-2026-47884
- GHSA-pc63-qcmh-9cmg
Timeline
- 2026-08-27: disclosed