Finding and attribution
In the Execution::Next runner, a resolver that raises GraphQL::UnauthorizedError from its authorization hook is treated as authorized, so the resolver still runs and can disclose data or perform side effects.
Product: graphql-ruby. AI system: GitHub Security Lab Taskflow Agent. Team / organization: GitHub Security Lab.
CVE identifiers: Not established in the cited evidence.
AI and human contribution (source account): GHSL credits its Taskflow Agent with discovery and says GHSL team members manually verified the issue. The report identifies the Execution::Next code path and affected versions; no separate CVE is listed.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: The GHSL advisory documents the authorization bypass and fix; it does not claim exploitation in the wild.
Remediation status: fix documented. GHSL’s timeline says the issue was fixed 2026-07-17 and graphql-ruby v2.6.6 released 2026-07-21; patch state in dependent applications is not checked.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 21 Jul 2026. AI attribution dated 21 Jul 2026. Sources checked 14 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Not available · no assessment established here. Documented technical effects: data disclosure, data modification, privilege escalation.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
No source-backed CVSS assessment is established in this catalog.
Case-level evidence: data disclosure, data modification, privilege escalation.
Prerequisites / affected scope: Execution::Next schemas following the documented authorized? UnauthorizedError pattern; resolver runs despite authorization failure..
Exploitation evidence: The cited source does not establish exploitation in the wild.. Impact source · checked 16 Nov 2026.
Documented fix: GHSL’s timeline says the issue was fixed 2026-07-17 and graphql-ruby v2.6.6 released 2026-07-21; patch state in dependent applications is not checked.