Restricted-field disclosure via indexed COUNT permission bypass
Published Jul 20, 2026 · Updated Jul 20, 2026
Incorrect authorization in SurrealDB before 3.1.0 allows remote authenticated users to recover indexed restricted-field values through COUNT queries. The Index::Count, IndexCountScan, and legacy index-count planner paths count matching index entries without applying the field-level SELECT permission check. Table-level SELECT access and an index on the protected field are required; repeated guesses reveal field contents but cannot cross isolation boundaries, modify data, or interrupt service.
Summary
What happened
Incorrect authorization in SurrealDB before 3.1.0 allows remote authenticated users to recover indexed restricted-field values through COUNT queries. The Index::Count, IndexCountScan, and legacy index-count planner paths count matching index entries without applying the field-level SELECT permission check. Table-level SELECT access and an index on the protected field are required; repeated guesses reveal field contents but cannot cross isolation boundaries, modify data, or interrupt service.
The record
- CVE
- CVE-2026-63742
- Published
- Jul 20, 2026
- Updated
- Jul 20, 2026
- Vendor
- SurrealDB
- Product
- SurrealDB
- Classifications
- CWE-863, T1213.006
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 20, 2026CVE publishedPublication date reported by the CVE source.
- Jul 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.1.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo