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.
CVE-2026-63736
Score 4.1 from GitHub Security Advisory published 2026-07-20. a secondary CVSS source baseline 4.1; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- 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 computedSeverity41% × 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, 2026SurrealDB before 3.2.0 SSRF via JWKS URL hostname resolution | Advisories | VulnCheck
https://www.vulncheck.com/advisories/surrealdb-before-ssrf-via-jwks-url-hostname-resolutionSSRF 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-qr67Vendor 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.
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 10:49 UTCEG score recompute
- 2026-07-26 10:49 UTCGHSA enrichment
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:22 UTCEG score recompute
- 2026-07-22 23:47 UTCEG score recompute
- 2026-07-22 23:47 UTCGHSA enrichment
- 2026-07-22 23:44 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 14:58 UTCEG score recompute
- 2026-07-20 14:58 UTCGHSA enrichment
- 2026-07-20 13:05 UTCEG score recompute
- 2026-07-20 13:05 UTCGHSA enrichment
- 2026-07-20 12:20 UTCEG score recompute
- 2026-07-20 12:17 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-14721EG 10.0EPSS p95CRITICAL
- CVE-2018-18843EG 10.0CRITICAL
- CVE-2018-19047EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-3774EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2018-1789NVD 8.4EG 9.9CRITICAL
Frequently asked(5)
What is CVE-2026-63736?
When was CVE-2026-63736 disclosed?
Is CVE-2026-63736 actively exploited?
What is the CVSS score of CVE-2026-63736?
How do I remediate CVE-2026-63736?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-63736
Is Your Infrastructure Affected by CVE-2026-63736?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.