CVE-2026-41699
Unsafe deserialization in Spring for GraphQL may lead to RCE via crafted paginated requests
Is CVE-2026-41699 being exploited?
Not confirmed. CVE-2026-41699 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.43% probability of exploitation in the next 30 days.
How severe is CVE-2026-41699?
CVE-2026-41699 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-41699?
Yes. A fix has been recorded for CVE-2026-41699. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-41699 affect?
CVE-2026-41699 affects Spring for GraphQL: v2.0.0–2.0.3, v1.4.0–1.4.5, v1.3.0–1.3.8. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-41699?
Upgrade to patched Spring for GraphQL release
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
RCE via unsafe deserialization during paginated GraphQL handling; attacker can run arbitrary code
Patch when possible
- affected>= 2.0.0 and < 2.0.3.1
- affected>= 1.4.0 and < 1.4.5.1
- affected>= 1.3.0 and < 1.3.9
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.