CVE-2026-63761
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.
Scoring
- Severity
- MEDIUM
- CVSS base score
- 5.3
- CVSS 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
- EPSS probability
- 0.28%
- CWE
- CWE-327
- Published
- 2026-07-20
- Last modified
- 2026-07-28
Affected products
- surrealdb surrealdb
- surrealdb surrealdb
Weakness type
Related vulnerabilities
- CVE-2026-81822 — AVEVA Pipeline Integrity Monitor Use of a Broken or Risky Cryptographic Algorithm
- CVE-2026-69382 — Microsoft Exchange Server Information Disclosure Vulnerability
- CVE-2026-16693 — IBM i is Affected By Cryptographic Algorithm Weakness in DCM []
- CVE-2026-81859 — Multiple security vulnerabilities are addressed with IBM Cloud Pak for Business Automation iFixes for August 2026.
- CVE-2026-76133 — Ebyte NA111-M Use of a Broken or Risky Cryptographic Algorithm
- CVE-2026-39944 — Ceph: CephX AES Authentication error
- CVE-2025-30156 — Ceph: AES-CBC misuse in CephX and RADOSGW enables authentication bypass and credential forgery
- CVE-2026-77151 — lin-snow Ech0 crypto.go MD5Encrypt risky encryption