CVE-2026-47884
Description
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.
Statement
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.
Mitigation
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.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 9.8 | N/A | 9.8 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | High | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.
Integrity
Technical Impact: Modify Files or Directories
The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.
Confidentiality
Technical Impact: Read Files or Directories
The attacker may be able read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of protection mechanisms such as authentication, it has the potential to lock out product users.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
