CVE-2026-63761 json
SurrealDB before 3.1.0 Algorithm Downgrade via ES512
published 4mo ago modified last mo. also GHSA-fwg2-gr34-q3w8 , EUVD-2026-45932
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 20%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- crates.io surrealdb 3.1.0
- surrealdb surrealdb 3.1.0
- github.com/surrealdb/surrealdb@bd043d7 commit
- github.com/surrealdb/surrealdb#7226 pull request
Is CVE-2026-63761 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3mo ago
Exploit prediction
0.28% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 5.3 | 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 |
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |
| CNA | 4.0 | 5.3 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| GitHub | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | surrealdb | <3.1.0 |
3.1.0 |
Affected products
- surrealdb surrealdb
Classification
- Weakness
-
- CWE-327 Use of a Broken or Risky Cryptographic Algorithm
References
-
github.com
/surrealdb/surrealdb/pull/7226
web
-
github.com
/surrealdb/surrealdb/commit/bd043d73dad583219d7df2b91f81ab0054c53730
web
-
github.com
/surrealdb/surrealdb/security/advisories/GHSA-fwg2-gr34-q3w8
vendor-advisory, web, mitigation
-
vulncheck.com
/advisories/surrealdb-before-algorithm-downgrade-via-es512
third-party-advisory, web
-
nvd.nist.gov
/vuln/detail/CVE-2026-63761
advisory
-
github.com
/surrealdb/surrealdb
package
Sources
- CVE List CVE-2026-63761
- GitHub Advisory GHSA-fwg2-gr34-q3w8
- NVD CVE-2026-63761
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.