CVE-2026-54698
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedHasura 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn Hasura versions prior to 2.49.2 and 2.45.5, a user can exploit computed fields returning SETOF table rows by using WHERE clause predicates as an oracle to infer row-level permission-restricted values. Although direct access to filtered rows is blocked, the WHERE clause evaluation reveals whether values exist, enabling efficient brute-force enumeration of restricted data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2.45.0, <= 2.45.5>= 2.46.0, <= 2.49.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Hasura versionRun 'hasura --version' or check the Docker/container image tag. Compare against the affected ranges: versions before 2.45.5, or between 2.46.0 and 2.49.1.Affected if The installed version is prior to 2.45.5 or falls between 2.46.0 and 2.49.1 inclusive.
-
Locate computed fields returning SETOF table rowsQuery the Hasura metadata API endpoint '/v1/query' with 'export_metadata' to inspect 'computed_fields' definitions. Look for computed fields where 'return_type' references a table and includes 'SETOF'.Affected if Any computed field is defined with a return type of 'SETOF <table_name>'.
-
Verify row-level permissions exist on the underlying tableQuery the metadata for 'select_permissions' on the table referenced by the computed field. Check if permission rules are defined in the 'permissions' section.Affected if Row-level select permissions are configured on the table that the computed field returns.
-
Confirm computed field is exposed via GraphQL APIInspect the GraphQL schema via the '/v1/graphql' introspection query. Verify the computed field appears in the query type for the table.Affected if The computed field is queryable through the GraphQL endpoint and accepts WHERE clause filtering.
You are affected if your Hasura version is below 2.45.5 or between 2.46.0-2.49.1, and you have computed fields that return SETOF table rows with row-level permissions configured on the underlying table.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Hasura to version 2.49.2 or 2.45.5 to apply the security fix.
Hasura v2.49.2 or v2.45.5
- Upgrade Hasura to version 2.49.2 (or 2.45.5 for the LTS branch) to resolve the incorrect authorization vulnerability
- After upgrading, verify that row-level permissions on computed fields (SETOF some_table) are properly enforced
- Test that the where clause on computed fields no longer allows inferring filtered row values through brute-force oracles
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54698 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-54698 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data