CVE-2022-39359

Metabase's GeoJSON validation doesn't prevent redirects to blocked URLs

MEDIUM

6.5

CVSS Score

Published: October 26, 2022 at 12:00 AM UTC

Updated: June 17, 2026 at 04:58 AM UTC

1 product affected across 1 vendorMetabase

Using metabase by metabase?

Get instant alerts when new vulnerabilities affect metabase - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM6.5

Exploit prediction

EPSS 0.7%

SSVC

No known exploit

Description

Metabase is data visualization software. Prior to versions 0.44.5, 1.44.5, 0.43.7, 1.43.7, 0.42.6, 1.42.6, 0.41.9, and 1.41.9, custom GeoJSON map URL address would follow redirects to addresses that were otherwise disallowed, like link-local or private-network. This issue is patched in versions 0.44.5, 1.44.5, 0.43.7, 1.43.7, 0.42.6, 1.42.6, 0.41.9, and 1.41.9. Metabase no longer follow redirects on GeoJSON map URLs. An environment variable `MB_CUSTOM_GEOJSON_ENABLED` was also added to disable custom GeoJSON completely (`true` by default).

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Metabase · Metabasecontainer

95%

v < 0.41.9v < 0.42.6v < 0.43.7v < 0.44.5v < 1.41.9v < 1.42.6v < 1.43.7v < 1.44.50.41.0 ≤ v < 0.41.90.42.0 ≤ v < 0.42.60.43.0 ≤ v < 0.43.70.44.0 ≤ v < 0.44.51.41.0 ≤ v < 1.41.91.42.0 ≤ v < 1.42.61.43.0 ≤ v < 1.43.71.44.0 ≤ v < 1.44.5

Affected range stops below 0.41.9, so it looks safe — our inference, not a vendor statement

Affected range stops below 0.42.6, so it looks safe — our inference, not a vendor statement

Affected range stops below 0.43.7, so it looks safe — our inference, not a vendor statement

Affected range stops below 0.44.5, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.41.9, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.42.6, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.43.7, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.44.5, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

https://github.com/metabase/metabase/commit/057e2d67fcbeb6b48db68b697e022243e3a5771e

References (2)

PatchThird Party Advisory

Source: [email protected]

https://github.com/metabase/metabase/commit/057e2d67fcbeb6b48db68b697e022243e3a5771e

Third Party Advisory

Source: [email protected]

https://github.com/metabase/metabase/security/advisories/GHSA-w5j7-4mgm-77f4

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.5MEDIUMGitHub_M

Attack Vector: NETWORK
Complexity: LOW
Privileges: LOW
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: HIGH
Integrity: NONE
Availability: NONE

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-200CWE-601

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card