CVE-2026-72900
Metabase information exposure
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in x.58.24, x.59.21, x.60.17, x.61.11, x.62.9, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Metabase allows an authenticated, low-privileged attacker to read the entire Metabase application database.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Metabase 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