CVE-2026-47884

A flaw was found in the XsltView component of Spring MVC applications. This vulnerability could allow a remote, unauthenticated attacker to perform Server-Side Request Forgery (SSRF), enabling them to make unauthorized requests from the server, and potentially achieve Remote Code Execution (RCE), allowing them to execute arbitrary code on the affected system. This occurs when an application uses a broad URL mapping that results in view rendering without explicitly specifying the view name, allowing an attacker to control which stylesheet is loaded.

Red Hat rates this vulnerability as Critical, a higher severity than the Medium rating assigned by the Spring project. This vulnerability requires a remote, unauthenticated attacker with no user interaction to trigger Server-Side Request Forgery and, depending on the XSLT processor's configuration, Remote Code Execution — conditions that meet Red Hat's definition of Critical impact regardless of the upstream CVSS vector.

Exploitation requires a Spring MVC application to use XsltView in combination with a broad ("/**") URL mapping that renders a view without explicitly specifying the view name. This is not the default configuration for Spring MVC applications; applications that explicitly specify view names, or do not use XsltView, are not exposed.

Where this precondition is met, no additional privileges, authentication, or user interaction are required, and full compromise of the affected system is possible via Remote Code Execution. Red Hat is not aware of any built-in safeguard in affected Spring Framework versions that reduces this impact once the vulnerable configuration pattern is present.

Independent parties, including CISA-ADP, have also assessed this vulnerability as Critical, consistent with Red Hat's rating.

The CVSS score(s) listed for this vulnerability do not reflect the associated product's status, and are included for informational purposes to better understand the severity of this vulnerability.

There is no upstream-provided workaround; the Spring project's guidance is to upgrade to a fixed version. However, applications can avoid this vulnerability without upgrading by not using XsltView together with a broad/catch-all URL mapping that omits an explicit view name — explicitly specifying the view name for any controller or handler that renders a view prevents an attacker from controlling which XSLT stylesheet is loaded.

For Red Hat Fuse 7, which is in Extended Life Support Phase 2 and will not receive a fix for this issue, this configuration-based workaround is the only available mitigation.