Skip to content
major vulnerability· requires attention

Unauthenticated SQL injection yields administrator takeover of Metabase, a widely used BI product; full data and instance compromise risk with CVSS 10.0.

Applications

CVE-2026-72898

10.0
Critical
KEV · Exploited in wildEPSS 94%Patch availableAug 11, 2026

Unauthenticated SQL injection in Metabase '/reset_password' allows admin takeover.

common questions

Is CVE-2026-72898 being exploited?

Yes. CVE-2026-72898 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2026-72898?

CVE-2026-72898 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-72898?

Yes. A fix has been recorded for CVE-2026-72898. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-72898 affect?

CVE-2026-72898 affects Metabase server instances, Metabase /reset_password endpoint. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-72898?

Isolate Metabase, restrict network access, rotate admin creds, apply vendor patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Metabase server instancesMetabase /reset_password endpoint
impact

Remote unauthenticated SQL injection via /reset_password enables arbitrary SQL, creation/compromise of admin accounts, data exfiltration and full instance compromise.

action required

Immediate action required

affected versions
Metabase Metabase
  • affected>= x.58.0 and < x.58.24
  • affected>= x.59.0 and < x.59.21
  • affected>= x.60.0 and < x.60.17
  • affected>= x.61.0 and < x.61.11
  • affected>= x.62.0 and < x.62.9
  • affected>= x.63.0 and < x.63.5
vendor says fixed inx.58.24, x.59.21, x.60.17, x.61.11, x.62.9, x.63.5

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free