CyberRota Analysis
AI-GeneratedSurrealDB versions prior to 3.1.0 incorrectly substitute the ES384 algorithm for ES512 when configured for JWT access, leading to authentication failures for users providing the correct P-521 key. This issue can disrupt user access and integration with external systems that rely on valid ES512 signatures, although it does not compromise data confidentiality or integrity. Organizations using SurrealDB with JWT authentication should prioritize upgrading to version 3.1.0 to avoid these authentication issues.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD 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.
Related CVEs
Other vulnerabilities affecting the same vendor(s)