Spring for GraphQL CVE-2026-59286

Exploitation requires two concurrent conditions: (1) the GraphiQL UI must be enabled and reachable from the attacker's vantage point - GraphiQL should not be exposed to public or untrusted networks and is disabled by default in production-hardened Spring configurations; and (2) the attacker must be positioned to intercept or modify HTTP responses from the CDN hosting GraphiQL's JavaScript dependencies, achieved via CDN-infrastructure compromise, BGP hijack, ARP spoofing on a shared LAN, or a rogue Wi-Fi access point. A user (developer or administrator) must load the GraphiQL page in a browser for the injected payload to execute. Applications that disable GraphiQL or serve it exclusively on localhost are not exploitable regardless of CDN posture. Authentication to the Spring application is not required of the attacker, but the CDN-intercept precondition limits this to targeted or supply-chain-class attacks rather than opportunistic mass exploitation.

The CVSS 8.1 score is driven by full C/H/I/H/A/H impact metrics, but the High Attack Complexity (AC:H) is the critical moderating factor: successful exploitation requires an attacker to either compromise the CDN origin or establish a network-level MITM position between the victim's browser and the CDN, neither of which is trivially achievable at scale. EPSS at 0.11% (2nd percentile) confirms that exploitation is not currently occurring at meaningful volume, and the vulnerability is absent from CISA KEV. A material inconsistency in the provided CVSS vector warrants attention: the vector specifies UI:N (no user interaction), yet the described impact is explicitly 'arbitrary code on the browser loading the GraphiQL page' - browser-based attacks inherently require a user to navigate to the page, making UI:R the technically correct metric; defenders should treat the scope as narrower than the raw score implies. Even a mid-sized municipal IT team in Inowroclaw running an internal developer portal faces meaningful exposure only if GraphiQL is network-accessible beyond trusted hosts AND an adversary has already achieved a CDN-intercept position. In practice, GraphiQL defaults to disabled or is restricted to localhost in production-hardened deployments, which substantially reduces real-world blast radius, though insider threats and CDN supply-chain compromise scenarios remain credible threat vectors worth addressing.

An attacker with a MITM position on the network segment between a developer's workstation and the CDN serving GraphiQL's JavaScript dependencies substitutes a legitimate CDN response with a malicious bundle containing a credential-harvesting payload. When the developer opens the GraphiQL IDE to test a GraphQL mutation, the injected script silently reads the developer's session token or GraphQL API key from the browser's local storage and exfiltrates it to an attacker-controlled endpoint. No public exploit code has been identified at time of analysis, and the CDN-intercept precondition constrains this scenario to targeted attacks.