CVE-2026-63736

MEDIUMPre-NVD 4.14.1
EchelonGraph scoreHIGH confidence

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

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

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

SurrealDB before 3.2.0 contains a server-side request forgery vulnerability in the JWKS fetcher that validates only the URL hostname string against allow-lists without checking resolved IP addresses. An Owner role attacker can point an access method at an allow-listed hostname resolving to private or loopback addresses, causing the server to issue GET requests to internal addresses that would be blocked by direct URL.

CVSS v3
4.1
EG Score
4.1(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
Severity41% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
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.2.0 SSRF via JWKS URL hostname resolution | Advisories | VulnCheck

https://www.vulncheck.com/advisories/surrealdb-before-ssrf-via-jwks-url-hostname-resolution
github Patch Available

SSRF via JWKS URL — allow-listed hostname resolving to a private IP · Advisory · surrealdb/surrealdb · GitHub

https://github.com/surrealdb/surrealdb/security/advisories/GHSA-5x4x-2946-qr67

Vendor Advisories for CVE-2026-63736(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 24× in last 7d / 24× 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-26 14:54 UTCEPSS rescore
  2. 2026-07-26 14:54 UTCEPSS rescore
  3. 2026-07-26 10:49 UTCEG score recompute
  4. 2026-07-26 10:49 UTCGHSA enrichment
  5. 2026-07-25 14:18 UTCEPSS rescore
  6. 2026-07-25 14:18 UTCEPSS rescore
  7. 2026-07-24 14:18 UTCEPSS rescore
  8. 2026-07-24 14:18 UTCEPSS rescore
  9. 2026-07-23 14:18 UTCEPSS rescore
  10. 2026-07-23 14:18 UTCEPSS rescore
  11. 2026-07-23 03:22 UTCEG score recompute
  12. 2026-07-22 23:47 UTCEG score recompute
  13. 2026-07-22 23:47 UTCGHSA enrichment
  14. 2026-07-22 23:44 UTCGHSA enrichment
  15. 2026-07-22 14:08 UTCEPSS rescore
  16. 2026-07-22 14:08 UTCEPSS rescore
  17. 2026-07-21 15:25 UTCEPSS rescore
  18. 2026-07-21 15:25 UTCEPSS rescore
  19. 2026-07-20 14:58 UTCEG score recompute
  20. 2026-07-20 14:58 UTCGHSA enrichment
  21. 2026-07-20 13:05 UTCEG score recompute
  22. 2026-07-20 13:05 UTCGHSA enrichment
  23. 2026-07-20 12:20 UTCEG score recompute
  24. 2026-07-20 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-63736?
CVE-2026-63736 is a medium vulnerability published on July 20, 2026. SurrealDB before 3.2.0 contains a server-side request forgery vulnerability in the JWKS fetcher that validates only the URL hostname string against allow-lists without checking resolved IP addresses. An Owner role attacker can point an access method at an allow-listed hostname resolving to private…
When was CVE-2026-63736 disclosed?
CVE-2026-63736 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-63736 actively exploited?
CVE-2026-63736 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 86.5% of all scored CVEs.
What is the CVSS score of CVE-2026-63736?
CVE-2026-63736 has a CVSS v3 base score of 4.1 (NVD).
How do I remediate CVE-2026-63736?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63736, 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-63736

Explore →

Is Your Infrastructure Affected by CVE-2026-63736?

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