Vmware Spring for GraphQL up to 1.0.6/1.3.8/1.4.5/2.0.3 access control

Summaryinfo

A vulnerability, which was classified as critical, has been found in Vmware Spring for GraphQL up to 1.0.6/1.3.8/1.4.5/2.0.3. This impacts an unknown function. This manipulation causes access control. This vulnerability is tracked as CVE-2026-41856. The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Vmware Spring for GraphQL up to 1.0.6/1.3.8/1.4.5/2.0.3. It has been declared as critical. Affected by this vulnerability is an unknown functionality. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. As an impact it is known to affect confidentiality. The summary by CVE is:

The Spring GraphQL annotation detection mechanism for @Controller data fetchers may not correctly resolve annotations on methods within type hierarchies. This can be an issue if such annotations are used for authorization decisions. When all conditions are met, security annotations can be ignored at runtime. 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; 1.0.0 through 1.0.6.

The advisory is shared at spring.io. This vulnerability is known as CVE-2026-41856 since 04/22/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/11/2026). MITRE ATT&CK project uses the attack technique T1068 for this issue.

Upgrading to version 1.0.7, 1.3.9, 1.4.6 or 2.0.4 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-36214). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

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.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.4.0
• 1.4.1
• 1.4.2
• 1.4.3
• 1.4.4
• 1.4.5
• 2.0.0
• 2.0.1
• 2.0.2
• 2.0.3

License

• commercial

Website

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

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion