Spring for GraphQL Unsafe Deserialization in pagination support

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.

Affected scope and exposure questions

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

Recommended response

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

Evidence timeline and material changes

1. Published upstream

   Aug 27, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Aug 27, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Aug 27, 2026

Sources and claim methodology

• Source referencespring.io

Related CVEs

• SpeechBrain < 1.1.1 Arbitrary Code Execution via CKPT.yaml ParsingAlso CWE-502
• Potential for deserialization of untrusted types in Spring Cloud StreamAlso CWE-502
• Deserialization allow-list silently bypassed: setBeanClassLoader replaces deserializer but mapper keeps stale referenceAlso CWE-502
• Unauthenticated Remote Code Execution in GraphQL Composite Data APISame generic ecosystem
• Unauthenticated Privilege Escalation via System Configuration Image Upload ProcessorSame generic ecosystem
• DNG SDK | Out-of-bounds Read (CWE-125)Same generic ecosystem