Read the docs

Missing authentication in SurrealDB revoke RPC method lets callers revoke tokens

Priority LOW 24CWE-306Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Security bypass
Confidentiality · integrity · availability
None · Low · Low
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-306.

Summary

SurrealDB from 3.0.0 before 3.3.0 has missing authentication (CWE-306) in its revoke RPC method. Low-privileged or unauthenticated callers can invalidate other users' refresh tokens without proving possession of them. Attackers can obtain grant identifiers through ACCESS SHOW ALL with VIEWER permission or from leaked tokens, then permanently revoke refresh tokens to force re-authentication.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Description from the CNA

SurrealDB from 3.0.0 before 3.3.0 contains a missing authentication vulnerability in the revoke RPC method that allows low-privileged or unauthenticated callers to invalidate other users' refresh tokens without proof of possession. Attackers can obtain grant identifiers via ACCESS SHOW ALL with VIEWER permission or leaked tokens, then permanently revoke refresh tokens to force re-authentication.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00277 20th percentileScored 2026-11-07
Fix Fixed surrealdb (surrealdb): 3.3.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
surrealdbsurrealdb3.0.0 to before 3.3.03.3.0Patch availableCNA
  • surrealdb Vendorsurrealdb Affected 3.0.0 to before 3.3.0 Fixed in 3.3.0 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:surrealdb:surrealdb:*:*:*:*:*:*:*:*——surrealdb
  • cpe:2.3:a:surrealdb:surrealdb:*:*:*:*:*:*:*:* Versions — — ·surrealdb

Remediation

Upgrade SurrealDB to version 3.3.0, which fixes the flaw in versions from 3.0.0 before 3.3.0.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

  • Fix · CNA surrealdb (surrealdb) Fixed in 3.3.0

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    surrealdb 3.3.0

    11 records Highest priority Priority LOW 11 LOW

    Other records, highest priority first

    • TI-2026-71159 Cross-tenant access in SurrealDB through the USE statementPriority LOW 39
    • TI-2026-71150 Cross-tenant access in SurrealDB through namespace and database selectionPriority LOW 37
    • TI-2026-71157 Field permission bypass in SurrealDB via PATCH copy and movePriority LOW 31

Timeline

  1. 2026-10-12 Threatist record created from CVE-2026-109342
  2. 2026-10-12 Alias added: GHSA-6872-82p6-5gmv
  3. 2026-10-15 CISA SSVC decision points changed

References

  • TI-2026-84300 SurrealDB index planner lets users infer restricted fields CVSS 4.0MEDIUM 5.3
  • TI-2026-84304 Server-side request forgery in SurrealDB via JWKS URL default ports CVSS 4.0MEDIUM 5.1
  • TI-2026-45344 SurrealDB before 3.1.0 Session Hijacking via /rpc sessions CVSS 4.0HIGH 8.7
  • TI-2024-38452 SurrealDB before 1.1.0 Denial of Service via HTTP Headers CVSS 4.0HIGH 8.7
  • TI-2026-45347 SurrealDB before 3.1.0 Denial of Service via JSON Parser CVSS 4.0HIGH 8.7
  • TI-2026-45334 SurrealDB before 3.1.0 Denial of Service via malformed RPC use CVSS 4.0HIGH 8.7
See all 76 →

Sources