# CVE-2026-47884: Spring Framework Improper Path Limitation in XsltView > Attackers can achieve SSRF and remote code execution in Spring MVC applications using XsltView with specific wildcard mappings. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 27 Aug 2026 - **Updated:** 27 Aug 2026 - **Also known as:** CLEANSTART-2026-BM08082, CLEANSTART-2026-GO94409, CLEANSTART-2026-XY63591, DEBIAN-CVE-2026-47884, ECHO-c06d-d2db-b927, GHSA-pc63-qcmh-9cmg, MINI-36m9-rhf3-22x9, MINI-6f5j-p7xw-rpqx, MINI-6qxh-4m8p-5ffv, MINI-8x8j-ffph-93qh, MINI-93jj-rpf9-4fw7, MINI-mxg3-8g96-9mxg, ROOT-APP-MAVEN-CVE-2026-47884, UBUNTU-CVE-2026-47884 ## What is CVE-2026-47884? CVE-2026-47884 is a critical server-side request forgery vulnerability in Vmware Spring Framework, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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 Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2026-47884? 12 open source packages ship an affected version, including org.springframework:spring-webmvc. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.springframework:spring-webmvc` | Maven | All versions to 5.2.25.RELEASE | None | | `org.springframework:spring-webmvc` | Maven | All versions to 5.2.25.RELEASE | None | | `org.springframework:spring-webmvc` | Maven | From 5.3.0 to 5.3.49 | None | | `org.springframework:spring-webmvc` | Maven | From 5.3.0 to 5.3.49 | None | | `org.springframework:spring-webmvc` | Maven | From 6.0.0 to 6.0.30 | None | | `org.springframework:spring-webmvc` | Maven | From 6.0.0 to 6.0.30 | None | | `org.springframework:spring-webmvc` | Maven | From 6.1.0 to 6.1.28 | None | | `org.springframework:spring-webmvc` | Maven | From 6.1.0 to 6.1.28 | None | | `org.springframework:spring-webmvc` | Maven | From 6.2.0 to 6.2.19 | None | | `org.springframework:spring-webmvc` | Maven | From 6.2.0 to 6.2.19 | None | | `org.springframework:spring-webmvc` | Maven | From 7.0.0 | 7.0.9 | | `org.springframework:spring-webmvc` | Maven | From 7.0.0 | 7.0.9 | Products: Vmware Spring Framework. ## How do I fix CVE-2026-47884? Upgrade org.springframework:spring-webmvc to 7.0.9 or later. ## Is CVE-2026-47884 being exploited? There is no known exploitation of CVE-2026-47884 in the wild and no public exploit code. Public exploit code: - CVE-2026-47884:覆盖 15 条 Spring / Tomcat 官方安全公告,8 条被 NVD 报成 CRITICAL 9.x 而厂商官方评 LOW/MEDIUM,另 7 条两边一致 —— 差别只在厂商有没有自己提交 CVSS。工具告诉你中了哪几条、官方评多少分、是否真满足触发条件,以及官方叫你升的版本 Maven Central 上有没有。 (github_poc): https://github.com/xiaoqiMikko/spring-cvss-check ## Other vulnerabilities in Vmware Spring Framework - [CVE-2026-47890](https://insights.sbomify.com/CVE-2026-47890/): Spring Framework Server Sent Event stream corruption while rendering fragments (critical 9.8) - [CVE-2026-47891](https://insights.sbomify.com/CVE-2026-47891/): Spring Framework maxInMemorySize Bypassed in Jaxb2Decoder (critical 9.8) - [CVE-2026-47892](https://insights.sbomify.com/CVE-2026-47892/): Spring Framework Header Predicate Bypass in WebFlux Functional Endpoints (critical 9.8) - [CVE-2026-59313](https://insights.sbomify.com/CVE-2026-59313/): Server Sent Event stream corruption in Spring MVC functional web framework (critical 9.8) - [CVE-2016-1000027](https://insights.sbomify.com/CVE-2016-1000027/): Pivotal Spring Framework contains unsafe Java deserialization methods (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-47884 and fix it if it is affected. What it is: CVE-2026-47884 is a critical server-side request forgery vulnerability in Vmware Spring Framework, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-47884 in the wild and no public exploit code. Affected packages and fixed versions: - org.springframework:spring-webmvc (Maven): affected all versions up to 5.2.25.RELEASE; no fix listed - org.springframework:spring-webmvc (Maven): affected all versions up to 5.2.25.RELEASE; no fix listed - org.springframework:spring-webmvc (Maven): affected from 5.3.0 up to 5.3.49; no fix listed - org.springframework:spring-webmvc (Maven): affected from 5.3.0 up to 5.3.49; no fix listed - org.springframework:spring-webmvc (Maven): affected from 6.0.0 up to 6.0.30; no fix listed - org.springframework:spring-webmvc (Maven): affected from 6.0.0 up to 6.0.30; no fix listed - org.springframework:spring-webmvc (Maven): affected from 6.1.0 up to 6.1.28; no fix listed - org.springframework:spring-webmvc (Maven): affected from 6.1.0 up to 6.1.28; no fix listed - org.springframework:spring-webmvc (Maven): affected from 6.2.0 up to 6.2.19; no fix listed - org.springframework:spring-webmvc (Maven): affected from 6.2.0 up to 6.2.19; no fix listed - org.springframework:spring-webmvc (Maven): affected from 7.0.0; fixed in 7.0.9 - org.springframework:spring-webmvc (Maven): affected from 7.0.0; fixed in 7.0.9 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-47884/ (Markdown: https://insights.sbomify.com/CVE-2026-47884/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47884 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47884 - OSV: https://osv.dev/vulnerability/CVE-2026-47884 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-47884/ Summaries are generated and may contain mistakes; the official description above is the record.