SurrealDB before 3.1.0 silently substitutes the ES384 algorithm when a JWT access method is configured with ALGORITHM ES512 (DEFINE ACCESS ... TYPE JWT ALGORITHM ES512), because the underlying jsonwebtoken crate (v10.x) has no ES512 variant and the mapping defaults to ES384 without any error, warning, or log message. Users who supply the correct P-521 key for ES512 experience authentication handshake failures due to the curve mismatch with ES384 (which expects P-384), and tokens are rejected by external systems expecting genuine ES512 signatures. The flaw cannot be used to forge tokens or compromise data confidentiality or integrity, as ES384 remains cryptographically strong.
References
| Link | Resource |
|---|---|
| https://github.com/surrealdb/surrealdb/security/advisories/GHSA-fwg2-gr34-q3w8 | Vendor Advisory Mitigation |
| https://www.vulncheck.com/advisories/surrealdb-before-algorithm-downgrade-via-es512 | Third Party Advisory |
Configurations
History
22 Jul 2026, 15:07
| Type | Values Removed | Values Added |
|---|---|---|
| CPE | cpe:2.3:a:surrealdb:surrealdb:*:*:*:*:*:*:*:* | |
| First Time |
Surrealdb
Surrealdb surrealdb |
|
| References | () https://github.com/surrealdb/surrealdb/security/advisories/GHSA-fwg2-gr34-q3w8 - Vendor Advisory, Mitigation | |
| References | () https://www.vulncheck.com/advisories/surrealdb-before-algorithm-downgrade-via-es512 - Third Party Advisory |
20 Jul 2026, 12:19
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-07-20 12:19
Updated : 2026-07-22 15:07
NVD link : CVE-2026-63761
Mitre link : CVE-2026-63761
CVE.ORG link : CVE-2026-63761
JSON object : View
Products Affected
surrealdb
- surrealdb
CWE
CWE-327
Use of a Broken or Risky Cryptographic Algorithm
