CVE-2026-63761: SurrealDB before 3.1.0 Algorithm Downgrade via ES512
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-63761?
The severity of CVE-2026-63761 is categorized as medium with a score of 4.3.
How do I fix CVE-2026-63761?
To fix CVE-2026-63761, upgrade SurrealDB to version 3.1.0 or later.
What does CVE-2026-63761 affect?
CVE-2026-63761 affects SurrealDB versions prior to 3.1.0.
What type of vulnerability is CVE-2026-63761?
CVE-2026-63761 is an algorithm downgrade vulnerability related to the JWT access method.
What is the impact of CVE-2026-63761?
The impact of CVE-2026-63761 is the potential security risk of using a weaker algorithm (ES384) instead of the intended algorithm (ES512) without any notifications.