What is 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.
The record classifies CVE-2026-41699 under weakness class CWE-502. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 138 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 8.1 — HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H - EPSS (FIRST)
- 0.6% probability of exploitation in the next 30 days, higher than 50.9% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 6.1/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-06-11, last modified 2026-06-30
Is CVE-2026-41699 being exploited?
It currently carries a trending score of 18 in the Threadlinqs vulnerability feed.
Affected products and versions
- Spring: for GraphQL
How to fix CVE-2026-41699
No vendor patch reference has been recorded for CVE-2026-41699 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2026-41699
1 tracked threat in the Threadlinqs corpus references CVE-2026-41699, either in the campaign’s CVE list or as an indicator on the campaign record.
Sources
Enriched from CVE.org, FIRST EPSS. Last verified by Threadlinqs on .