VMware Spring for GraphQL up to 1.0.7/1.3.9/1.4.6/2.0.4 GraphiQL Page information disclosure

Summaryinfo

A vulnerability labeled as problematic has been found in VMware Spring for GraphQL up to 1.0.7/1.3.9/1.4.6/2.0.4. Affected by this issue is some unknown functionality of the component GraphiQL Page. Executing a manipulation can lead to information disclosure. The identification of this vulnerability is CVE-2026-59288. The attack may be launched remotely. There is no exploit available.

Detailsinfo

A vulnerability has been found in VMware Spring for GraphQL up to 1.0.7/1.3.9/1.4.6/2.0.4 and classified as problematic. This vulnerability affects an unknown part of the component GraphiQL Page. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. CVE summarizes:

The GraphiQL page bundled with Spring for GraphQL sends requests to the GraphQL endpoints of the application. An attacker can share a malicious URL so that the victim's browser might leak confidential information to the attacker's website. Spring for GraphQL 2.0.0 - 2.0.4 Spring for GraphQL 1.4.0 - 1.4.6 Spring for GraphQL 1.1.0 - 1.3.9 Spring for GraphQL 1.0.0 - 1.0.7

The advisory is shared for download at spring.io. This vulnerability was named CVE-2026-59288 since 07/04/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 08/27/2026). The MITRE ATT&CK project declares the attack technique as T1592.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• VMware

Name

• Spring for GraphQL

Version

• 1.0.0
• 1.0.1
• 1.0.2
• 1.0.3
• 1.0.4
• 1.0.5
• 1.0.6
• 1.0.7
• 1.3.0
• 1.3.1
• 1.3.2
• 1.3.3
• 1.3.4
• 1.3.5
• 1.3.6
• 1.3.7
• 1.3.8
• 1.3.9
• 1.4.0
• 1.4.1
• 1.4.2
• 1.4.3
• 1.4.4
• 1.4.5
• 1.4.6
• 2.0.0
• 2.0.1
• 2.0.2
• 2.0.3
• 2.0.4

License

• commercial

Website

• Vendor: https://www.vmware.com/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion