Use of a Broken or Risky Cryptographic Algorithm Affecting surrealdb package, versions <3.1.0-beta.1
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-RUST-SURREALDB-17797680
- published2 Jul 2026
- disclosed1 Jul 2026
- creditUnknown
Introduced: 1 Jul 2026
New CVE NOT AVAILABLE CWE-327 (opens in a new tab)How to fix?
Upgrade surrealdb to version 3.1.0-beta.1 or higher.
Overview
Affected versions of this package are vulnerable to Use of a Broken or Risky Cryptographic Algorithm due to the silent substitution of the ES512 algorithm with ES384 in the DEFINE ACCESS process when configuring JWT access methods. An attacker can cause authentication handshake failures by specifying ES512 with a P-521 key, resulting in curve mismatches and denial of access when tokens are verified by systems expecting ES512 signatures.
Workaround
This vulnerability can be mitigated by reconfiguring JWT access methods to use a supported algorithm such as ES384 with a P-384 key pair or another supported algorithm, and by reviewing and updating any DEFINE ACCESS statements specifying ES512.