PatchSiren cyber security CVE debrief
CVE-2026-47884 Spring CVE debrief
CVE-2026-47884 is a critical vulnerability in Spring Framework, a popular Java framework for building web applications. The vulnerability can result in Server-Side Request Forgery (SSRF) and Remote Code Execution (RCE) attacks if the application has an /** mapping that results in view rendering, and where the view name is not explicitly specified. This could allow attackers to manipulate requests and execute malicious code. Defenders and developers using Spring Framework should assess their exposure and prioritize remediation due to the high severity of the vulnerability.
- Vendor
- Spring
- Product
- Spring Framework
- CVSS
- CRITICAL 9.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-27
- Original CVE updated
- 2026-09-10
- Advisory published
- 2026-08-27
- Advisory updated
- 2026-09-10
Who should care
Defenders and developers using Spring Framework should assess exposure and prioritize remediation due to the high severity of the vulnerability and potential for SSRF and RCE attacks.
Why it matters
CVE-2026-47884 is a critical vulnerability in Spring Framework that can lead to SSRF and RCE attacks. Defenders and developers should assess exposure, prioritize remediation, and implement additional security measures to prevent attacks.
- Potential for Server-Side Request Forgery (SSRF) attacks
- Potential for Remote Code Execution (RCE) attacks
- Need for version updates and security patches
- Importance of monitoring for suspicious activity
Technical summary
The vulnerability in Spring Framework can result in SSRF and RCE attacks if the application has an /** mapping that results in view rendering, and where the view name is not explicitly specified. Affected versions include Spring Framework 7.0.0 - 7.0.8, 6.2.0 - 6.2.19, 6.1.0 - 6.1.28, 6.0.0 - 6.0.30, 5.3.0 - 5.3.49, and 5.2.25.RELEASE and earlier. The issue arises from the XsltView in a Spring MVC application, which can be exploited under certain conditions. To mitigate this vulnerability, it is essential to update to the latest patched versions of Spring Framework and implement additional security measures.
Defensive priority
High
Recommended defensive actions
- Review and update Spring Framework versions to the latest patched versions
- Implement additional security measures to prevent SSRF and RCE attacks
- Monitor for suspicious activity and update incident response plans accordingly
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
Evidence notes
The CVE record and NVD detail page provide information on the vulnerability in Spring Framework, which can result in SSRF and RCE attacks under certain conditions. The vendor advisory from VMware is also available.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-47884 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-47884
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-47884 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-47884
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://spring.io/security/cve-2026-47884
[email protected] - Vendor Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.