PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-47891 Spring CVE debrief

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-27T06:17:20.287Z and has not been modified since then. The NVD entry is currently Analyzed. This critical vulnerability affects the Spring WebFlux application when it relies on the Aalto XML processor to parse XML input, not correctly enforcing the maxInMemorySize limit, potentially leading to remote code execution. It impacts multiple versions of the Spring Framework, including 5.2.25.RELEASE and earlier, 5.3.0 - 5.3.49, 6.0.0 - 6.0.30, 6.1.0 - 6.1.28, 6.2.0 - 6.2.19, and 7.0.0 - 7.0.8, with a CVSS score of 9.8, indicating critical severity. Immediate attention is required to assess and mitigate risk. The debrief is based on CVE Program and NVD records, with additional vendor advisory information.

Vendor
Spring
Product
Spring Framework
CVSS
CRITICAL 9.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-27
Original CVE updated
2026-09-02
Advisory published
2026-08-27
Advisory updated
2026-09-02

Who should care

IT and security teams responsible for maintaining and securing applications built with the Spring Framework should prioritize assessing and mitigating this vulnerability. This includes reviewing current versions in use, applying patches or updates, and implementing compensating controls as necessary.

Technical summary

The CVE-2026-47891 vulnerability affects the Spring WebFlux application when it relies on the Aalto XML processor to parse XML input. The application does not correctly enforce the maxInMemorySize limit, potentially leading to remote code execution. The vulnerability impacts multiple versions of the Spring Framework, including 5.2.25.RELEASE and earlier, 5.3.0 - 5.3.49, 6.0.0 - 6.0.30, 6.1.0 - 6.1.28, 6.2.0 - 6.2.19, and 7.0.0 - 7.0.8. It has been assigned a CVSS score of 9.8, indicating a critical severity level.

Defensive priority

This critical vulnerability affects multiple versions of the Spring Framework, allowing for potential remote code execution. Immediate attention is required to assess and mitigate risk.

Recommended defensive actions

  • Assess the current Spring Framework versions in use within your environment.
  • Verify if the versions in use are within the affected ranges.
  • Apply patches or updates to vulnerable versions as recommended by the vendor.
  • Implement compensating controls such as monitoring and network segmentation if patches cannot be applied immediately.
  • Review and update inventory records to reflect accurate version information.

Evidence notes

The CVE-2026-47891 record indicates a critical vulnerability in the Spring Framework, specifically in how it handles XML input with the Aalto XML processor. Versions affected include Spring Framework 5.2.25.RELEASE and earlier, 5.3.0 - 5.3.49, 6.0.0 - 6.0.30, 6.1.0 - 6.1.28, 6.2.0 - 6.2.19, and 7.0.0 - 7.0.8. The vulnerability has a CVSS score of 9.8 and is classified as CRITICAL.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-47891 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-47891

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-47891 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-47891

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.