Code execution via pagination deserialization
Published Aug 27, 2026 · Updated Aug 27, 2026
Unsafe deserialization in Spring for GraphQL 2.0.0 through 2.0.4 allows remote attackers to execute code via paginated GraphQL requests. The Jackson 2.x pagination path deserializes attacker-controlled request values and can instantiate classpath gadget classes that execute unintended logic. Exploitation requires an exposed Connection field, Jackson 2.x, and suitable gadget classes on the application classpath.
Summary
What happened
Unsafe deserialization in Spring for GraphQL 2.0.0 through 2.0.4 allows remote attackers to execute code via paginated GraphQL requests. The Jackson 2.x pagination path deserializes attacker-controlled request values and can instantiate classpath gadget classes that execute unintended logic. Exploitation requires an exposed Connection field, Jackson 2.x, and suitable gadget classes on the application classpath.
The record
- CVE
- CVE-2026-59285
- Published
- Aug 27, 2026
- Updated
- Aug 27, 2026
- Vendor
- Spring
- Product
- Spring for GraphQL
- Classifications
- CWE-502, CAPEC-586, T1190
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 27, 2026CVE publishedPublication date reported by the CVE source.
- Aug 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0.0 <=2.0.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo