CVE-2026-41699 | Unsafe Deserialization in Spring GraphQL

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.

Published: 2026-06-11 Last update: 2026-06-12 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2026-41699 is rated Moderate Risk (49.3/100): CVSS High severity, with low exploitation likelihood (EPSS 0.68%). Mandatory action: Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-41699

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.41% 0.68% +0.27%
2 2026-06-13 0.34% 0.41% +0.07%
3 2026-06-11 0.34%

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-41699

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.1 3.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
2.2 5.9 [email protected]
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
3.9 5.9 [email protected]

Weakness enumeration for CVE-2026-41699

GitHub Security Advisory for CVE-2026-41699

GHSA-px92-q6rc-6mwv · Severity: high — Spring for GraphQL applications are vulnerable to Unsafe Deserialization when processing...

Affected software / configurations for CVE-2026-41699

Vendor Product Version Raw CPE
vmware spring_for_graphql >= 1.3.0, < 1.3.9 cpe:2.3:a:vmware:spring_for_graphql:*:*:*:*:*:*:*:*
vmware spring_for_graphql >= 1.4.0, < 1.4.6 cpe:2.3:a:vmware:spring_for_graphql:*:*:*:*:*:*:*:*
vmware spring_for_graphql >= 2.0.0, < 2.0.4 cpe:2.3:a:vmware:spring_for_graphql:*:*:*:*:*:*:*:*

References for CVE-2026-41699

cvelogic Threat Intelligence