Skip to content
major vulnerability· requires attention

Unauthenticated SQL injection (CVSS 10) in popular BI tool Metabase enabling wide-scale data theft and disruption; likely to attract broad attention and requires org-wide action.

Applications

CVE-2026-72899

10.0
Critical
EPSS 0.56%Patch availableAug 11, 2026

Unauthenticated SQL injection in Metabase via public shared card/dashboard.

common questions

Is CVE-2026-72899 being exploited?

Not confirmed. CVE-2026-72899 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.56% probability of exploitation in the next 30 days.

How severe is CVE-2026-72899?

CVE-2026-72899 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-72899?

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

What does CVE-2026-72899 affect?

CVE-2026-72899 affects Metabase (publicly shared cards and dashboards). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-72899?

Disable public sharing, restrict access, network-block Metabase, and 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 (publicly shared cards and dashboards)
impact

Unauthenticated SQL injection against connected DBs via public shares; allows arbitrary SQL execution, data exfiltration, modification, and potential downstream 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