CVE-2026-92813

MEDIUMPre-NVD 4.94.9—
EchelonGraph scoreHIGH confidence

Score 4.9 from GitHub Security Advisory published 2026-09-16. a secondary CVSS source baseline 4.9; sources differ by 0.0.

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

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

Metabase through 0.63.18 fails to properly validate the unspecified address 0.0.0.0 in custom GeoJSON URLs, allowing unauthenticated attackers to reach loopback services. Attackers can save a malicious GeoJSON entry with 0.0.0.0 and trigger requests that return loopback service responses to unauthenticated callers.

CVSS v3
4.9
EG Score
4.9(high)
EG Risk
38(Track)
EG Risk 38/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
Severity49% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

September 16, 2026

Last Modified

September 17, 2026

Advisory Details (4)

Auto-updated Sep 16, 2026
No patch confirmed yet.
generic

Metabase through 0.63.18 SSRF via GeoJSON URL validation bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/metabase-through-0.63.18-ssrf-via-geojson-url-validation-bypass
generic

GitHub - metabase/metabase: The easy-to-use open source Business Intelligence and Embedded Analytics tool that lets everyone work with data :bar_chart: · GitHub

https://github.com/metabase/metabase
generic

metabase/src/metabase/geojson/api.clj at v0.61.2 · metabase/metabase · GitHub

https://github.com/metabase/metabase/blob/v0.61.2/src/metabase/geojson/api.clj#L26-L47
generic

oss/metabase.md at main · geo-chen/oss · GitHub

https://github.com/geo-chen/oss/blob/main/metabase.md#finding-2-geojson-ssrf-bypass-via-0000-address

Vendor Advisories for CVE-2026-92813(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 16× in last 7d / 16× 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-09-20 20:16 UTCEPSS rescore
  2. 2026-09-20 13:42 UTCEG score recompute
  3. 2026-09-20 13:41 UTCGHSA enrichment
  4. 2026-09-19 13:58 UTCEG score recompute
  5. 2026-09-19 13:58 UTCGHSA enrichment
  6. 2026-09-18 19:28 UTCEPSS rescore
  7. 2026-09-18 14:15 UTCEG score recompute
  8. 2026-09-18 14:15 UTCGHSA enrichment
  9. 2026-09-17 19:32 UTCEPSS rescore
  10. 2026-09-17 14:25 UTCEG score recompute
  11. 2026-09-17 14:25 UTCGHSA enrichment
  12. 2026-09-17 13:52 UTCEG score recompute
  13. 2026-09-17 13:52 UTCGHSA enrichment
  14. 2026-09-16 21:23 UTCEG score recompute
  15. 2026-09-16 20:36 UTCEG score recompute
  16. 2026-09-16 20:34 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-92813?
CVE-2026-92813 is a medium vulnerability published on September 16, 2026. Metabase through 0.63.18 fails to properly validate the unspecified address 0.0.0.0 in custom GeoJSON URLs, allowing unauthenticated attackers to reach loopback services. Attackers can save a malicious GeoJSON entry with 0.0.0.0 and trigger requests that return loopback service responses to…
When was CVE-2026-92813 disclosed?
CVE-2026-92813 was first published in the National Vulnerability Database on September 16, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92813 actively exploited?
CVE-2026-92813 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 78.4% of all scored CVEs.
What is the CVSS score of CVE-2026-92813?
CVE-2026-92813 has a CVSS v3 base score of 4.9 (NVD).
How do I remediate CVE-2026-92813?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-92813, 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-92813

Explore →

Is Your Infrastructure Affected by CVE-2026-92813?

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

Start Free Scan →Browse All CVEs