Spring for GraphQL: Unsafe Deserialization
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 software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Java / Kotlin (Maven) | org.springframework.graphql:spring-graphql | >= 2.0.0, < 2.0.4, >= 1.4.0, < 1.4.6, >= 1.3.0, <= 1.3.8 | 2.0.4, 1.4.6 |
References
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H- Weakness (CWE)
CWE-502- Platform
- Java / Kotlin (Maven)
- Package
org.springframework.graphql:spring-graphql- Disclosed
- 11.06.2026
- Updated
- 11.10.2026 12:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-px92-q6rc-6mwv - CC BY 4.0
Vulnerability history: org.springframework.graphql:spring-graphql
All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 4
- First → latest
- 09.2023 06.2026
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- High 3
- Low 1
Disclosures per year
- 2023: 1
- 2024: 0
- 2025: 0
- 2026: 3
-
Spring for GraphQL: Unsafe Deserialization this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.