Skip to content

Spring for GraphQL: Annotation Detection Vulnerability

High severity GitHub Reviewed Published Jun 11, 2026 to the GitHub Advisory Database • Updated Aug 21, 2026

Package

maven org.springframework.graphql:spring-graphql (Maven)

Affected versions

>= 2.0.0, <= 2.0.3
>= 1.4.0, <= 1.4.5
>= 1.3.0, <= 1.3.8
>= 1.0.0, <= 1.0.6

Patched versions

2.0.4
1.4.6

Description

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.

References

Published by the National Vulnerability Database Jun 11, 2026
Published to the GitHub Advisory Database Jun 11, 2026
Reviewed Aug 21, 2026
Last updated Aug 21, 2026

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(28th percentile)

Weaknesses

Improper Access Control

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Learn more on MITRE.

CVE ID

CVE-2026-41856

GHSA ID

GHSA-phxq-526m-79px

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.