CVE-2026-72898: Metabase SQL Injection
Metabase · listed in the CISA catalog of actively exploited vulnerabilities since 2026-08-11.
- CVSS v3.1 (CVE record)
- 10.0
- critical
- EPSS (exploit probability, 30 days)
- 99%
- among the highest 0.1% of all CVEs
- Added to CISA KEV
- 2026-08-11
- US federal due date 2026-08-14
- Automatable (CISA SSVC)
- yes
- technical impact: total
CVE-2026-72898 explained
CVE-2026-72898 is an SQL injection vulnerability in Metabase server software. A remote, unauthenticated attacker can inject arbitrary SQL through the '/reset_password' database endpoint and gain administrator access to the Metabase instance. CISA lists it as known to be exploited, so affected instances need urgent attention.
Impact
An attacker needs only network access to the Metabase instance. No credentials or user interaction are required. A successful attack gives administrator access, with high impact to confidentiality, integrity and availability, and the impact can reach beyond the vulnerable component. CISA rates it as automatable, meaning it can be exploited at scale. Its technical impact is total. CISA also lists it as known to be exploited by attackers.
Who is affected
Metabase is affected on six release branches. They are versions ≥ x.58.0, < x.58.24, ≥ x.59.0, < x.59.21, ≥ x.60.0, < x.60.17, ≥ x.61.0, < x.61.11, ≥ x.62.0, < x.62.9 and ≥ x.63.0, < x.63.5. The fixed versions are x.58.24, x.59.21, x.60.17, x.61.11, x.62.9 and x.63.5. Each branch is fixed in the version listed for it.
Written with AI from the data on this page and checked against it automatically.
Official description
Metabase allows a remote, unauthenticated attacker to inject arbitrary SQL via the '/reset_password' database endpoint and gain administrator access to the connected Metabase instance.
CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- MetabaseAffectedFixed in
- ≥ x.58.0, < x.58.24
- ≥ x.59.0, < x.59.21
- ≥ x.60.0, < x.60.17
- ≥ x.61.0, < x.61.11
- ≥ x.62.0, < x.62.9
- ≥ x.63.0, < x.63.5
- x.58.24
- x.59.21
- x.60.17
- x.61.11
- x.62.9
- x.63.5
| Product | Affected | Fixed in |
|---|---|---|
| Metabase |
|
|
How to fix it
- Update to a fixed version: x.58.24, x.59.21, x.60.17, x.61.11, x.62.9, x.63.5.
- Vendor advisory: github.com/metabase/metabase/security/advisories/GHSA-vwf…
- CISA's deadline for US federal agencies: 2026-08-14 (passed) – a useful benchmark for everyone else, too.
What to do
- Upgrade each Metabase instance to the fixed version for its branch:
x.58.24,x.59.21,x.60.17,x.61.11,x.62.9orx.63.5. - Apply any mitigations in the vendor advisory if you cannot upgrade immediately.
- Restrict network access to Metabase so it is not reachable from the internet, or only reachable by trusted users.
- Check instances for signs of compromise, such as unexpected administrator accounts or changes, following CISA's forensics triage requirements.
- If mitigations are unavailable, discontinue use of the product as CISA's required action states.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- Yes – attackers can automate it at scale
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Questions about CVE-2026-72898
- Do attackers need an account to exploit CVE-2026-72898?
- No. The description states that a remote, unauthenticated attacker can exploit it. No user interaction is required either.
- Is this vulnerability being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-08-11 and set a US federal due date of 2026-08-14. Known ransomware use is listed as unknown.
- Which version should I upgrade to?
- Upgrade to the fixed release on your branch. These are
x.58.24,x.59.21,x.60.17,x.61.11,x.62.9orx.63.5.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.