Deserialization in Spring For Graphql

CVE-2026-41699

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.

Vulnerability class: Insecure Deserialization

Published · last modified .

CVSS v3 metric

CVSS v3 base score 8.1 (High). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.

EPSS exploit prediction

EPSS: 0.007 (50.5th percentile), scored .

Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 50th percentile — 50.5% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2026-41699: held from 0.004 to 0.007.

EPSS over last 30 days · oldest: 0.004 · newest: 0.007 · change: +0.002

Affected products

Weakness classification (CWE)

References

Frequently asked questions

What is CVE-2026-41699?
CVE-2026-41699 is a high-severity vulnerability in Spring For Graphql, classified under Deserialization of Untrusted Data. CVSS score: 8.1/10. Published 2026-06-11.
How severe is CVE-2026-41699?
High severity. CVSS v3 base score is 8.1 out of 10.