External risk intelligence

Metabase SQL Injection Leads to Administrator Access

CVE advisorySeverity: CRITICAL (CVSS 10.0)

CVE-2026-72898

Metabase is a business intelligence application typically deployed as a public or internet-accessible web service to facilitate data access, and the vulnerable endpoint is part of the application's authentication flow, making it reachable by design in standard deployments.

SQL Injection

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This vulnerability impacts Metabase, a business intelligence platform, by allowing unauthenticated attackers to inject malicious SQL code. This could potentially grant unauthorized administrators access to the connected Metabase instance and its data.

  • Attackers can insert malicious commands into password reset requests.
  • Critical systems may face unauthorized access and data compromise.
  • Confirm Metabase usage and assess exposure to sensitive data.

Attack Path

How an attacker could exploit the issue

An attacker can target the Metabase application's password reset feature to inject malicious SQL commands. By sending specially crafted input to the `/reset_password` endpoint, an unauthenticated user can manipulate the database queries, potentially gaining administrative control over the Metabase instance.

  • No authentication required.
  • Inject SQL via password reset.
  • Gain administrator access.

Live Threat

Current exploitation, exposure, and threat context

A remote, unauthenticated attacker could inject arbitrary SQL via the password reset endpoint, potentially granting them administrator access and control over the connected Metabase instance. This could allow them to view, modify, or delete sensitive data and alter service behavior.

  • Connected Metabase instance data.
  • Via unauthenticated SQL injection.
  • Unauthorized administrator access.

Operational Fix

Recommended remediation, mitigation, and detection steps

Responsibility for addressing this critical vulnerability likely falls to the Platform Engineering or Infrastructure teams who manage the Metabase deployment. The first practical step is to identify all instances of Metabase within the environment, determine their exposure (internal/external), and confirm which are business-critical. Subsequently, asset owners should be identified to prioritize and plan remediation, coordinating with the vendor for any necessary updates or patches.

  • Platform or Infrastructure teams own resolution.
  • Verify Metabase deployment reachability and criticality.
  • Coordinate vendor updates and plan remediation.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Metabase and what is it used for?

Metabase is a popular open-source business intelligence and data visualization platform. Organizations use it to connect to their databases, allowing teams to easily query, analyze, and create dashboards from company data without needing advanced technical coding skills.

What does CWE-89 mean for CVE-2026-72898?

CWE-89 refers to SQL Injection, a weakness where an application does not properly sanitize user input before including it in database queries. In the context of CVE-2026-72898, this allows an attacker to manipulate the underlying database commands by sending malicious input to the password reset feature, potentially gaining unauthorized administrative control.

How can an attacker trigger this vulnerability?

The vulnerability is triggered by sending a specially crafted request to the '/reset_password' endpoint. Because this endpoint does not require the user to be logged in, an attacker can initiate the attack remotely without any credentials. Normal, legitimate use of the password reset function does not trigger this flaw.

Why should I care about this CVE based on Halo Surface Signal?

Halo Surface Signal identifies this as a critical concern because Metabase is typically deployed as an internet-accessible service to support remote data access. Since the flaw exists within the authentication flow itself, it is reachable by design in standard public-facing deployments, significantly increasing the risk of unauthorized access.

What are the first steps to handle this in my environment?

Your initial priority is to locate every Metabase instance running in your network. Once found, assess the reachability of each instance to determine if it is exposed to the internet. Identify the teams responsible for these systems so they can prioritize the application of vendor-provided patches as soon as they become available.

References