CVE-2026-41699 is a high-severity (CVSS 8.1) Deserialization of Untrusted Data vulnerability in org.springframework.graphql:spring-graphql. A fix is available for org.springframework.graphql:spring-graphql — see the affected versions and patch details below.
Unsafe Deserialization in Spring GraphQL
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-41699.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-41699 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 382,795 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.springframework.graphql:spring-graphql☕org.springframework.graphql:spring-graphql☕org.springframework.graphql:spring-graphqlReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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 Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.graphql:spring-graphql | ≥ 2.0.0&&< 2.0.4 | 2.0.4org.springframework.graphql:spring-graphql:2.0.4 |
| ☕Maven | org.springframework.graphql:spring-graphql | ≥ 1.4.0&&< 1.4.6 | 1.4.6org.springframework.graphql:spring-graphql:1.4.6 |
| ☕Maven | org.springframework.graphql:spring-graphql | ≥ 1.3.0 | No fix |
Affected Products
spring for graphqlvmwareDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.graphql:spring-graphql, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.graphql:spring-graphql to 2.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-41699 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.
Frequently Asked Questions
Is CVE-2026-41699 in your dependencies?
Find it across Maven, including transitive dependencies.