CVE-2026-54698: hasura graphql-engine · Incorrect Authorization
Affects hasura graphql-engineSource CVE Database V5
Not known to be exploited · CVSS 6.0 Medium : upgrade to 2.49.2 or 2.45.5 when convenient.
Data as of 20 Nov 2026, 17:35 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.49.2, 2.45.5
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 7 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade graphql-engine and hasura/graphql-engine to 2.49.2 or 2.45.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| hasuragraphql-engine | Affected
| Fixed in
|
| hasuragraphql-engine | Affected
| Fixed in
|
GitHubhasura/graphql-enginepkg:github/hasura/graphql-engineOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in Hasura graphql-engine versions 2.49.2 and 2.45.5. Users should upgrade to at least these versions to remediate the issue. Patch status is confirmed by the version fixes stated in the description. No additional mitigations are indicated.
Description
Hasura is an open-source product that provides users GraphQL or REST APIs. Prior to 2.49.2 and 2.45.5, a user can use a where clause on a table computed field (returning SETOF some_table) to infer row values that ought to be filtered for their role based on some_table's row-level permissions. While such rows cannot be returned directly, like predicates on strings for instance allow values to be brute forced efficiently with the where clause as an oracle. This issue is fixed in versions 2.49.2 and 2.45.5.