Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-47884 – SSRF/RCE via XsltView – Spring Framework 5.2.x–7.0.8

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-47884 is a path-limitation vulnerability (CWE-22) in Spring Framework’s XsltView component that can be leveraged for Server-Side Request Forgery and Remote Code Execution. The flaw affects Spring MVC applications that use a "/**" mapping resulting in view rendering where the view name is not explicitly specified. The issue has been assigned a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: XsltView in Spring MVC resolves the view name into a file path without sufficiently restricting it, allowing path traversal (CWE-22) and related SSRF/RCE behavior (CWE-918).
  • Trigger conditions: the vulnerable application must expose a "/**" (catch-all) mapping that results in view rendering, and the requested view name must not be explicitly specified by the application, letting an attacker supply an arbitrary view/path value.
  • Attack vector: network-based, exploitable remotely with no authentication or user interaction (AV:N, AC:L, PR:N, UI:N).
  • Impact: successful exploitation can result in the application making attacker-controlled outbound requests (SSRF) and, depending on configuration, achieving remote code execution, with full compromise of confidentiality, integrity, and availability.

Affected software

  • 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

Severity

CVSS v3.1 Base Score: 9.8 (Critical)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: upgrade to the fixed release for your branch — 7.0.9 (open source); 7.0.8.1, 6.2.20, 6.1.29, 6.0.31, 5.3.50, and 5.2.26 are available to customers with Enterprise Support.
  • If patching is not immediately possible: review applications for "/**" mappings that result in view rendering without an explicitly specified view name, and remove or restrict such catch-all mappings until the framework can be upgraded.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge