CVE-2026-72898 kev in the critical feed json
Metabase SQL injection via password reset endpoint
published 3mo ago modified 2mo ago also EUVD-2026-55690
- cvss
- 10.0
- version 3.1, CNA
- cisa kev
- Exploited
- added 2026-08-11
- epss
- 98.2%
- EPSS 98.2% chance of exploitation in 30 days, percentile 99.9%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
cisa required action Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). 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.
- Metabase Metabase x.58.24, x.59.21, x.60.17, x.61.11, x.62.9, x.63.5
Is CVE-2026-72898 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa vex VA-26-222-01 updated cvss 10.0
Metabase SQL injection
-
Metabase >=x.58.0, <x.58.24, >=x.59.0, <x.59.21, >=x.60.0, <x.60.17, >=x.61.0, <x.61.11affected: vendor fix github.com
-
Metabase x.58.24, x.59.21, x.60.17, x.61.11fixed: vendor fix github.com
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
Timeline
- Published
- Added to CISA KEV
- CISA SSVC: exploitation active
- CISA patch deadline
Known exploited
- Added
- 3mo ago
- Patch by
- 2026-08-14 (2mo ago)
- Ransomware
- Not known
- Required action
- Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). 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.
- Vendor, product
- Metabase, Metabase
- CISA name
- Metabase SQL Injection Vulnerability
CISA SSVC
- Exploitation
- Active, exploited in the wild
- Automatable
- yes
- Technical impact
- total
- Assessed
- 3mo ago
Exploit prediction
98.21% chance of exploitation in the next 30 days, higher than 99.9% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 10.0 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H |
| CNA | 3.1 | 10.0 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
| CNA | 4.0 | 10.0 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- Metabase Metabase
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
github.com
/metabase/metabase/security/advisories/GHSA-vwf4-m7j8-wcjf
vendor-advisory, mitigation, patch
-
metabase.com
/blog/security-update
vendor-advisory, mitigation, patch
-
cve.org
/CVERecord?id=CVE-2026-72898
vdb-entry
-
raw.githubusercontent.com
/cisagov/CSAF/develop/csaf_files/IT/white/2026/va-26-222-01.json
third-party-advisory
-
cisa.gov
/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-72898
government-resource, us-government-resource
Sources
- CVE List CVE-2026-72898
- NVD CVE-2026-72898
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.