Description
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.
Severity (CVSS)
| Base score | 5.3 |
|---|---|
| Severity | Medium |
| Version | CVSS 4.0 |
| Vector | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N |
| Provided by | CNA |
Weaknesses
- CWE-327 — Use of a Broken or Risky Cryptographic Algorithm
Affected products
| Vendor | Product | Versions |
|---|---|---|
| surrealdb | surrealdb | 0 to <3.1.0; 3.1.0 |
References
- https://github.com/surrealdb/surrealdb/security/advisories/GHSA-fwg2-gr34-q3w8 (vendor-advisory)
- https://www.vulncheck.com/advisories/surrealdb-before-algorithm-downgrade-via-es512 (third-party-advisory)
Generated from the official CVE List on 21 Jul 2026 07:01 UTC.