Spring Framework maxInMemorySize Bypassed in Jaxb2Decoder (CVE-2026-47891) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-47891

Spring Framework maxInMemorySize Bypassed in Jaxb2Decoder

Answer in brief

CVE-2026-47891 records a Unknown severity vulnerability in Spring Framework maxInMemorySize Bypassed in Jaxb2Decoder. The current sources do not mark it as known exploited. The current feed maps Spring/Spring Framework (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 27, 2026Updated Aug 27, 2026Source checked Aug 27, 2026First seen by HOL Aug 27, 2026Material review Aug 27, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Spring/Spring Framework (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Spring/Spring Frameworkgeneric	7.0.0 \|\| 6.2.0 \|\| 6.1.0 \|\| 6.0.0 \|\| 5.3.0 \|\| 0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Spring/Spring Framework.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Aug 27, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 27, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 27, 2026

Sources and claim methodology

Source referencespring.io

Upstream source description

A Spring WebFlux application that relies on the Aalto XML processor to parse XML input does not correctly enforce the maxInMemorySize limit. 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

Quoted source text, attributed separately from HOL analysis.