# CVE-2026-92813: Metabase GeoJSON SSRF via 0.0.0.0 address bypass

Source: https://junglewise.ai/threats/cve-2026-92813-metabase-geojson-ssrf-via-0-0-0-0-address-bypass  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-16. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-92813 · Severity: medium · CVSS 4.9 · Published 2026-09-16

Metabase is an open-source business intelligence and data visualization tool used by organizations to create dashboards and reports. An unauthenticated attacker can bypass existing security controls that block requests to internal services by crafting a malicious GeoJSON URL using the 0.0.0.0 address. This allows the attacker to retrieve sensitive data from services running on the Metabase server itself (such as local databases or APIs) without proper authentication.

Technologies: [Metabase](https://junglewise.ai/threats/technologies/metabase). Vendors: [Metabase](https://junglewise.ai/threats/vendors/metabase).

## Quick answers

**Is CVE-2026-92813 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-92813 being exploited in the wild.

**How severe is CVE-2026-92813?** Medium severity, with a CVSS score of 4.9, published 16 September 2026.

**Which products and versions are affected?** Metabase through 0.63.18.

**Is there a fix for CVE-2026-92813?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-92813 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-92813?** Check whether you run Metabase at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

This vulnerability is a Server-Side Request Forgery (SSRF) bypass affecting the GeoJSON feature. The root cause is incomplete validation of the 0.0.0.0 wildcard address in the DNS resolver and host validation functions. While previous fixes added checks for link-local, loopback, and site-local addresses, Java's InetAddress.getByName("0.0.0.0") returns false for all three checks, allowing it to bypass validation. An authenticated admin can save a custom GeoJSON entry with a URL like http://0.0.0.0:9671/secret.json, and any unauthenticated user can trigger a GET /api/geojson/ request that causes the Metabase server to make an outbound connection to the loopback interface and return the response. The fix requires adding an explicit check for isAnyLocalAddress() in the validation logic.

## Affected products

- Metabase Metabase through 0.63.18

## Timeline

- 2026-06-03: disclosed: Finding 2 reported via email
- 2026-09-16: advisory: CVE-2026-92813 published

## References

- [https://github.com/geo-chen/oss/blob/main/metabase.md](https://github.com/geo-chen/oss/blob/main/metabase.md)
- [https://github.com/metabase/metabase](https://github.com/metabase/metabase)

## Related threats

- [Metabase unrestricted H2 functions in native queries](https://junglewise.ai/threats/cve-2026-103928-metabase-is-an-open-source-business-intelligence-and-analytics)
- [Metabase glossary API missing authorization checks](https://junglewise.ai/threats/cve-2026-86116-metabase-glossary-api-missing-authorization-checks)
- [Metabase information disclosure via native SQL queries](https://junglewise.ai/threats/cve-2026-72900-metabase-information-disclosure-via-native-sql-queries)
- [Metabase SQL injection in publicly shared dashboards](https://junglewise.ai/threats/cve-2026-72899-metabase-sql-injection-in-publicly-shared-dashboards)
- [Metabase SQL injection in password reset endpoint](https://junglewise.ai/threats/cve-2026-72898-metabase-sql-injection-in-password-reset-endpoint)