CVE-2026-72898

Metabase SQL injection, confirmed exploited in the wild.

Metabase contains a SQL Injection vulnerability that allows an unauthenticated remote attacker to inject arbitrary SQL into the Metabase application database, which can give them administrator access to the instance. From there, the attacker could change the application configuration, steal stored credentials for the connected databases, read any data accessible through those connections, and export data.

Check your domain free How we watch for this

98%chance of exploitation in the next 30 days (EPSS), 99th percentile

11 Augadded to CISA's Known Exploited Vulnerabilities list, 2026

14 Augfederal remediation deadline, already passed

Passedpast the deadline: patch now

CISA's name for it	Metabase SQL Injection Vulnerability
Vendor and product	Metabase · Metabase
Type	SQL injection · CWE-89
Exploited	Confirmed by CISA listed 11 August 2026
Likelihood	one of the most likely to be exploited of every vulnerability tracked
Deadline	14 August 2026 · already passed
Used in ransomware	Not reported
Advisories	www.metabase.com ↗ · github.com ↗ · www.cisa.gov ↗ · www.cisa.gov ↗

What to do

Three steps, in this order

Step 1

Apply the vendor fix.

Step 2

Treat the database behind it as exposed: rotate the credentials it stores and check for new admin users.

Step 3

Put a web application firewall rule in front of the endpoint until patched.

CISA's 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.

CISA's 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.

Is it on your estate?

Know before someone else finds it

Threat Landscape Monitoring fingerprints the software your internet-facing hosts disclose and matches it, every day, against this list and the exploitation scores. When a new entry touches something you run, you are told once, with the host and the fix. The free plan covers one domain.

Start free with one domain Run the free domain check

Questions

CVE-2026-72898 in short

Is CVE-2026-72898 being exploited?

Yes. CISA added CVE-2026-72898 to its Known Exploited Vulnerabilities catalogue on 11 August 2026, which it does only on evidence of exploitation in the wild.

What is the CISA deadline for CVE-2026-72898?

US federal agencies must remediate it by 14 August 2026. Everyone else should treat that date as the latest safe point to patch an internet-facing system.

How likely is CVE-2026-72898 to be exploited in the next 30 days?

FIRST's Exploit Prediction Scoring System gives it 98%, the 99th percentile of every CVE it scores.

How do I fix CVE-2026-72898?

Apply the vendor fix. Treat the database behind it as exposed: rotate the credentials it stores and check for new admin users. Put a web application firewall rule in front of the endpoint until patched.

Sources: CISA Known Exploited Vulnerabilities catalogue (released 10 November 2026) and FIRST EPSS. Page compiled automatically by SAK T.L.M, the threat-intelligence tool of SAK T.E.C, on 13 November 2026.