What is the CVSS score of CVE-2026-41699?

CVE-2026-41699 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.3%.

Which versions of Spring for GraphQL are affected by CVE-2026-41699?

Spring for GraphQL versions 1.3.0-1.3.8, 1.4.0-1.4.5, and 2.0.0-2.0.3 contain a critical remote code execution vulnerability exploitable by unauthenticated attackers through malformed GraphQL…. A patch is available.

How to fix or mitigate CVE-2026-41699?

Within 24 hours: Identify all applications using Spring for GraphQL and determine which expose paginated Connection fields. Within 7 days: Deploy vendor patches to all systems running affected versions (1.3.0-1.3.8, 1.4.0-1.4.5, 2.0.0-2.0.3); patches available per vendor advisory. Within 30 days: Verify successful deployment across all instances, review logs for pre-patch exploitation, and document remediation.

Spring for GraphQL CVE-2026-41699

EUVD-2026-36212 CRITICAL

Deserialization of Untrusted Data (CWE-502)

2026-06-11 vmware

GHSA-px92-q6rc-6mwv

Deserialization Java RCE Spring For Graphql

9.8

CVSS 3.1 · NVD

Severity by source

Vendor (vmware) PRIMARY

HIGH

qualitative

NVD

9.8 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

vuln.today AI

8.1 HIGH

Network-reachable and unauthenticated (AV:N/PR:N/UI:N), but exploitation requires a Connection field exposure plus suitable gadget classes on the classpath, which justifies AC:H; full RCE yields C/I/A:H.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

4.0 AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (vmware).

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Updated

Jun 12, 2026 - 19:43 vuln.today

v3 (cvss_changed)

Analysis Updated

Jun 12, 2026 - 19:43 vuln.today

v2 (cvss_changed)

Re-analysis Queued

Jun 12, 2026 - 19:37 vuln.today

cvss_changed

Severity Changed

Jun 12, 2026 - 19:37 NVD

HIGH CRITICAL

CVSS changed

Jun 12, 2026 - 19:37 NVD

8.1 (HIGH) 9.8 (CRITICAL)

Patch available

Jun 11, 2026 - 08:01 EUVD

Analysis Generated

Jun 11, 2026 - 07:01 vuln.today

DescriptionNVD

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.

Articles & Coverage 2

News 7 New Java Vulnerabilities - 7 High Severity, No Public POC Jun 12, 2026 News 7 New Java Vulnerabilities - 7 High Severity, No Public Exploits Jun 11, 2026

AnalysisAI

Remote code execution in Spring for GraphQL versions 1.3.0-1.3.8, 1.4.0-1.4.5, and 2.0.0-2.0.3 allows unauthenticated attackers to trigger unsafe deserialization by sending crafted paginated GraphQL queries against Connection-type fields. Exploitation requires that the application expose a paginated (Connection) field and that the classpath contains gadget classes leveraged during deserialization. No public exploit identified at time of analysis; EPSS sits at 0.34% (57th percentile) and the issue is not in CISA KEV, but a vendor patch is available.

Technical ContextAI

Spring for GraphQL is the VMware/Spring project's integration layer between Spring Boot applications and GraphQL Java, providing utilities for schema mapping, data fetching, and Relay-style pagination via Connection types. The vulnerability is rooted in CWE-502 (Deserialization of Untrusted Data): when processing pagination cursors for Connection fields, the framework deserializes data derived from attacker-controllable input without sufficiently restricting the object graph. If the application classpath contains gadget classes (common in large Spring/Java ecosystems, e.g. via Commons-Collections, Spring AOP, or similar libraries), the deserialization step can be coerced into invoking arbitrary code. The CPE cpe:2.3:a:spring:spring_for_graphql:*:*:*:*:*:*:*:* confirms the spring_for_graphql component itself is the affected product, not a downstream consumer.

RemediationAI

Vendor-released patch: upgrade Spring for GraphQL to 1.3.9, 1.4.6, or 2.0.4 depending on your maintenance branch, as published in the Spring advisory at https://spring.io/security/cve-2026-41699 and corroborated by https://nvd.nist.gov/vuln/detail/CVE-2026-41699 and https://vuldb.com/vuln/370356. If patching cannot be performed immediately, the most effective compensating control is to stop exposing paginated Connection fields to untrusted clients - either remove @Connection / Relay pagination from public schemas or restrict the GraphQL endpoint to authenticated, low-risk users via Spring Security (side effect: breaks pagination-dependent clients and any public API consumers). As a secondary measure, audit the classpath and remove unnecessary libraries known to provide deserialization gadgets (e.g. older Commons-Collections variants), keeping in mind that gadget surface is hard to fully enumerate, so this is mitigation, not a fix.