CVE-2026-63761

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory published 2026-07-20. a secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
4.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
4.3
EG Score
4.3(high)
EG Risk
19(Track)
EG Risk 19/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
5.9%
KEV
Not listed

Published

July 20, 2026

Last Modified

July 22, 2026

Advisory Details (2)

Auto-updated Jul 20, 2026
Patch available. Sources: github.
generic

SurrealDB before 3.1.0 Algorithm Downgrade via ES512 | Advisories | VulnCheck

https://www.vulncheck.com/advisories/surrealdb-before-algorithm-downgrade-via-es512
github Patch Available

ES512 silently downgraded to ES384 due to jsonwebtoken crate limitation · Advisory · surrealdb/surrealdb · GitHub

https://github.com/surrealdb/surrealdb/security/advisories/GHSA-fwg2-gr34-q3w8

Vendor Advisories for CVE-2026-63761(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 19× in last 7d / 19× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-24 14:18 UTCEPSS rescore
  2. 2026-07-24 14:18 UTCEPSS rescore
  3. 2026-07-23 14:18 UTCEPSS rescore
  4. 2026-07-23 14:18 UTCEPSS rescore
  5. 2026-07-23 03:22 UTCEG score recompute
  6. 2026-07-22 23:41 UTCEG score recompute
  7. 2026-07-22 23:41 UTCGHSA enrichment
  8. 2026-07-22 14:08 UTCEPSS rescore
  9. 2026-07-22 14:08 UTCEPSS rescore
  10. 2026-07-21 15:25 UTCEPSS rescore
  11. 2026-07-21 15:25 UTCEPSS rescore
  12. 2026-07-20 16:41 UTCEG score recompute
  13. 2026-07-20 16:41 UTCGHSA enrichment
  14. 2026-07-20 14:58 UTCEG score recompute
  15. 2026-07-20 14:57 UTCGHSA enrichment
  16. 2026-07-20 12:38 UTCEG score recompute
  17. 2026-07-20 12:37 UTCGHSA enrichment
  18. 2026-07-20 12:18 UTCEG score recompute
  19. 2026-07-20 12:17 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-63761?
CVE-2026-63761 is a medium vulnerability published on July 20, 2026. 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,…
When was CVE-2026-63761 disclosed?
CVE-2026-63761 was first published in the National Vulnerability Database on July 20, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63761 actively exploited?
CVE-2026-63761 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-63761?
CVE-2026-63761 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-63761?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63761, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-63761

Explore →

Is Your Infrastructure Affected by CVE-2026-63761?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs