Advisory record · GHSA-px92-q6rc-6mwv

Spring for GraphQL: Unsafe Deserialization

CVSS 8.1 HighEPSS 0.0043 · 37th percentile

Published by the GitHub Advisory Database at 11 Jun 2026, 09:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.springframework.graphql:spring-graphqlMaven>=2.0.0, <2.0.4 || >=1.4.0, <1.4.6 || >=1.3.0, <=1.3.82.0.4, 1.4.6
Identifiers
GHSA-px92-q6rc-6mwv · CVE-2026-41699
Weakness (CWE)
CWE-502
Published
11 Jun 2026
Updated
21 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Spring for GraphQL (spring-graphql) versions 2.0.0 through 2.0.3, 1.4.0 through 1.4.5, and 1.3.0 through 1.3.8 are vulnerable to unsafe deserialization when handling paginated queries. An attacker can send a crafted GraphQL request to an application that exposes a paginated (Connection) field, and this can lead to remote code execution if specific classes are on the classpath. Upgrade to spring-graphql 2.0.4 or 1.4.6. Versions 1.3.x have no fixed release listed, so upgrade to 1.4.6 or 2.0.4 instead.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.1 High 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H CNA (vmware)
  • CISA KEV Not listed.
  • EPSS 0.0043, the 37th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:19 UTC First seen by agentprime
  2. 31 Oct 2026, 14:19 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.