CVE-2026-41856GHSA-PHXQ-526M-79PX
Spring GraphQL Annotation Detection Vulnerability
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.0.3.1, 1.4.5.1, 1.3.9, 1.0.7, 2.0.4, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Spring Spring for GraphQL
From 2.0.0 · fixed in 2.0.3.1; From 1.4.0 · fixed in 1.4.5.1; From 1.3.0 · fixed in 1.3.9; From 1.0.0 · fixed in 1.0.7
- org.springframework.graphql:spring-graphqlMaven
From 2.0.0 · fixed in 2.0.4
- org.springframework.graphql:spring-graphqlMaven
From 1.4.0 · fixed in 1.4.6
- org.springframework.graphql:spring-graphqlMaven
From 1.3.0 · through 1.3.8
- org.springframework.graphql:spring-graphqlMaven
From 1.0.0 · through 1.0.6