CVE-2026-59285

Spring for GraphQL Unsafe Deserialization in pagination support

HIGH
8.1
CVSS Score
Published: August 27, 2026 at 05:57 PM UTC
Updated: September 2, 2026 at 07:32 PM UTC
2 products affected across 2 vendorsSpring for GraphqlSpring for GraphQL

Using Spring for GraphQL by Spring?

Get instant alerts when new vulnerabilities affect Spring for GraphQL - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.1
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

Spring for GraphQL applications are vulnerable to Unsafe Deserialization when processing paginated GraphQL queries. Spring for GraphQL 2.0.0 - 2.0.4

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.0.0 ≤ v < 2.0.4.1
Affected range stops below 2.0.4.1, so it looks safe — our inference, not a vendor statement
2.0.0 ≤ v ≤ 2.0.42.0.0

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (1)

Vendor Advisory
Source: cverecord
https://spring.io/security/cve-2026-59285

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.1HIGHCISA-ADP
Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-502

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card