published 11 Jun 2026 · updated 30 Jun 2026
Unsafe Deserialization in Spring GraphQL
8.1HighCVSS 8.1EPSS 0%
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 1.3.9, 1.4.5.1 and 2.0.3.1.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Spring | >=1.3.0 <1.3.9, >=1.4.0 <1.4.5.1, >=2.0.0 <2.0.3.1 | 1.3.9, 1.4.5.1, 2.0.3.1 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket