Security readout for executives and security teams
Plain-English summary
A critical Spring Framework flaw can let an unauthenticated remote attacker make vulnerable applications access internal resources or execute code. Exposure requires a specific combination: XsltView, a catch-all "/**" mapping that renders views, and no explicitly specified view name. Applications without that combination are not shown as exposed by the supplied description.
Executive priority
Treat as an immediate priority for exposed applications because the documented outcome includes unauthenticated remote code execution with complete confidentiality, integrity, and availability impact. First identify whether the required configuration exists; then follow Spring's advisory promptly. Do not assume every Spring application is vulnerable.
Technical view
CVE-2026-47884 is an improper path-limitation issue, classified as CWE-22, affecting Spring MVC XsltView behavior. Under the stated routing and implicit-view-name conditions, attacker-controlled requests may lead to SSRF or remote code execution. The supplied CVSS 3.1 score is 9.8: network-accessible, low complexity, unauthenticated, and requiring no user interaction.
Likely exposure
Internet-facing Spring MVC applications deserve immediate review, but exposure is configuration-dependent. The supplied affected ranges span 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.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not marked as included in KEV. Successful exploitation reportedly requires XsltView, a "/**" mapping that results in view rendering, and an implicitly determined view name. Public reachability would materially increase risk.
Researcher notes
The vulnerability is conditional rather than universal across listed versions. Assessment should correlate framework version, XsltView resolution, catch-all routing, implicit view naming, and external reachability. The bundle names no corrected versions or confirmed exploitation evidence, so remediation specifics and exploit prevalence remain incomplete.
Mitigation direction
- Inventory applications using affected Spring Framework versions and Spring MVC XsltView.
- Prioritize internet-facing applications with catch-all "/**" mappings.
- Explicitly specify view names where operationally appropriate.
- Follow Spring's security advisory for supported corrected releases or vendor-approved mitigations.
- Restrict unnecessary outbound connectivity to reduce potential SSRF impact.
Validation and detection
- Confirm each deployed Spring Framework version from build and runtime records.
- Search MVC configuration for XsltView usage and catch-all "/**" mappings.
- Determine whether matching handlers render views without explicitly specifying view names.
- Verify potentially vulnerable routes are reachable from untrusted networks.
- After remediation, confirm deployed versions and repeat configuration review.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-47884 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://spring.io/security/cve-2026-47884CVE reference, vmware
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.