CVE-2026-41699GHSA-PX92-Q6RC-6MWV
Unsafe Deserialization in Spring GraphQL
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.0.3.1, 1.4.5.1, 1.3.9, 2.0.4, 1.4.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Spring for GraphQL applications are vulnerable to Unsafe Deserialization when processing paginated GraphQL queries. An attacker can craft a malicious GraphQL request that can lead to Remote Code Execution when the application exposes a paginated (Connection) field and the classpath contains specific classes that can be leveraged during deserialization. Affected versions: Spring for GraphQL 2.0.0 through 2.0.3; 1.4.0 through 1.4.5; 1.3.0 through 1.3.8.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Spring Spring for GraphQL
From 2.0.0 · fixed in 2.0.3.1; From 1.4.0 · fixed in 1.4.5.1; From 1.3.0 · fixed in 1.3.9
- org.springframework.graphql:spring-graphqlMaven
From 2.0.0 · fixed in 2.0.4
- org.springframework.graphql:spring-graphqlMaven
From 1.4.0 · fixed in 1.4.6
- org.springframework.graphql:spring-graphqlMaven
From 1.3.0 · through 1.3.8