CVE-2026-72898: Metabase unauthenticated SQL injection via /api/session/reset_password

Exploited in the wild Critical 10.0 EPSS 98.8%

Metabase 58 and later lets an unauthenticated attacker inject SQL into the Metabase application database through the password-reset endpoint and gain administrator access, then change configuration, steal stored database credentials and read or export connected data (CVSS 10.0). Metabase found it being used as a 0-day against Metabase Cloud and released fixes on 2026-08-06; versions below 58 are not affected. CISA added it to the Known Exploited Vulnerabilities catalog on 2026-08-11.

CVE-2026-72898CVE identifier
10.0CVSS 4.0 base score (critical)
2026-08-11added to CISA's exploited list (US federal deadline 2026-08-14)
98.8%EPSS: chance of exploitation in the next 30 days (higher than 100% of CVEs)
2026-08-10published

What do these terms mean? CVE · CVSS score · exploited (KEV) · EPSS · backported fix · all terms

What to do now

Check whether you run the affected software and which version (commands below).
Install the fixed version for your system: see “Patch it” below.
Restart Metabase on the new JAR/image. If /api/session/reset_password was publicly reachable, afterwards delete all rows in the core_session table of the application database to revoke sessions.
If you cannot patch today, apply the temporary mitigation below and patch as soon as possible.
Because this flaw is being exploited, also check the server for signs of compromise.

Affected and fixed versions

Affected:

Metabase x.58.0 before x.58.24
x.59.0 before x.59.21
x.60.0 before x.60.17
x.61.0 before x.61.11
x.62.0 before x.62.9
x.63.0 before x.63.5
(x = 0 for OSS, 1 for Enterprise; versions below 58 are not vulnerable)

Fixed in:

Metabase 0.58.24 / 1.58.24
0.59.21 / 1.59.21
0.60.17 / 1.60.17
0.61.11 / 1.61.11
0.62.9 / 1.62.9
0.63.5 / 1.63.5

Patch it

Use the commands for your system. Distribution packages often keep an older version number with the fix backported, so compare with the fixed package versions in the table below, not only with the upstream version.

Docker images

docker pull metabase/metabase:v0.63.5          # OSS; use the fixed tag of your major version
# Enterprise: docker pull metabase/metabase-enterprise:v1.63.5
# recreate the container from the new image

Built from source

# JAR installs: replace metabase.jar with the fixed release and restart, e.g.
curl -fLO https://downloads.metabase.com/v0.63.5/metabase.jar

General update steps for every system are on the Linux and Unix & BSD pages; after updating, see which services to restart.

If you cannot patch yet

If you cannot upgrade at once, block /api/session/reset_password at your reverse proxy (vendor workaround).
After upgrading, if the endpoint was exposed: delete all rows in core_session, delete unrecognised API keys, review admin accounts, rotate credentials of all connected databases, and review warehouse logs and Metabase query history.

Look for signs of exploitation

Metabase application or ingress logs showing POST /api/session/reset_password with status 400 followed by GET /api/user/current with status 200 indicate a likely compromise (Metabase).

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.

https://www.metabase.com/blog/security-update ; https://github.com/metabase/metabase/security/advisories/GHSA-vwf4-m7j8-wcjf ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2026-72898

Sources

Page generated automatically from official sources on 2026-11-03 18:05 UTC and reviewed by an editor. Always confirm with your vendor's advisory.