Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-72898 – Unauthenticated SQL Injection / Admin Takeover – Metabase 0.58/1.58 through 0.63.4/

Be the first to know when new zero-days emerge:

Summary

CVE-2026-72898 is a critical, unauthenticated SQL injection vulnerability in Metabase, the open-source and Enterprise business intelligence platform. A remote attacker can inject arbitrary SQL through the password-reset endpoint against the Metabase application database and obtain administrator access to the instance. Metabase and NVD rate the flaw CVSS 10.0 (Critical), and it has been exploited in the wild as a zero-day.

Technical details

  • Root cause: Improper neutralization of special elements in an SQL command (CWE-89) in the handling of input to the password-reset flow, allowing arbitrary SQL to be injected against the Metabase application database.
  • Trigger conditions: A crafted request to the POST /api/session/reset_password endpoint. No authentication, no user interaction, and low attack complexity are required.
  • Attack vector: Network. The vulnerable endpoint is reachable by any client able to connect to the Metabase web interface.
  • Impact: Successful exploitation yields administrator access to the instance, enabling configuration changes, theft of stored credentials for connected databases, reading and exporting of any data accessible through those connections, and full compromise of confidentiality, integrity, and availability.

Affected software

  • Metabase 0.58.0–0.58.23 (Enterprise 1.58.0–1.58.23) — fixed in 0.58.24 / 1.58.24
  • Metabase 0.59.0–0.59.20 (Enterprise 1.59.0–1.59.20) — fixed in 0.59.21 / 1.59.21
  • Metabase 0.60.0–0.60.16 (Enterprise 1.60.0–1.60.16) — fixed in 0.60.17 / 1.60.17
  • Metabase 0.61.0–0.61.10 (Enterprise 1.61.0–1.61.10) — fixed in 0.61.11 / 1.61.11
  • Metabase 0.62.0–0.62.8 (Enterprise 1.62.0–1.62.8) — fixed in 0.62.9 / 1.62.9
  • Metabase 0.63.0–0.63.4 (Enterprise 1.63.0–1.63.4) — fixed in 0.63.5 / 1.63.5
  • Versions below 0.58 / 1.58 are not affected.

Severity

  • CVSS v3.1 Base Score: 10.0 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade to a patched release for your branch — 0.58.24, 0.59.21, 0.60.17, 0.61.11, 0.62.9, or 0.63.5 (or the corresponding 1.x Enterprise builds). Metabase Cloud instances have already been patched.
  • If no patch can be applied yet: Block or restrict access to the POST /api/session/reset_password endpoint until upgrading is possible.
  • Post-upgrade hardening: Revoke all active user sessions, review and remove unrecognized API keys, audit administrator accounts for unauthorized changes, rotate credentials for connected databases, and review query history and data-warehouse logs for suspicious access.
  • Indicators of compromise: A POST to /api/session/reset_password returning HTTP 400 followed by a successful GET /api/user/current (HTTP 200).

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw HTTP response body: window.MetabaseBootstrap =, MetabaseBootstrap"tag": "v..."

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge