Back

CRITICAL

Spring Framework Improper Path Limitation in XsltView

Published Aug 27, 2026

Description

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

Affected products

Remediation

Red Hat 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.

Red Hat 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.

Metrics

Weaknesses (1)

References (5)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner vmware
Published Aug 27, 2026
Updated Aug 27, 2026
Reserved May 20, 2026
CISA Vulnrichment
Updated Aug 27, 2026
NVD
Status Analyzed
Modified Sep 10, 2026
Red Hat
Severity Critical
Public date Aug 27, 2026