Metabase SQLi (CVE-2026-72898)

Overview

This workflow finds Metabase and sorts each host by whether its version falls in the CVE-2026-72898 range. Metabase is the BI console with a path to production warehouses. CVE-2026-72898 is SQL injection that CISA listed on KEV. The check reads /api/session/properties and flags the OSS and EE trains in the graph. Give it hostnames, IP addresses, or URLs you are authorised to test. The workflow fingerprints the product from the public page (title match on Metabase), reads the version from /api/session/properties with a fallback to the root body, and compares that number to the range table in the graph. Every host comes back affected or not, so a fleet advisory becomes an evidenced list for exposure management. CVE-2026-72898 is on CISA KEV (known exploited). Version flag is first. Hosts in range get a second node that only asks the password-reset path to sleep. It does not dump rows or write data.

Run it on a schedule when the estate changes. New hosts and delayed patch windows are the reason the same check is worth more the second week than the first.

Pipeline

1. Read the target list. Hosts, URLs, or ranges, one per line, become the scope.
2. Fingerprint each host as Metabase from the public page title, then GET /api/session/properties and parse the version. A host counts as affected only when the fingerprint matches and the version is inside the encoded range.
3. Confirm only those flagged hosts with a time-based sleep on the password-reset path.
4. Collect the per-host rows: product match, version, affected flag, confirmed flag, and any fetch error.
5. Emit the summary counts: hosts checked, product hits, affected, confirmed, and errors.

Inputs

• Target list. Hostnames, IP addresses, CIDR ranges, or URLs, one per line. JSONL with a url field also works. Point it at scope you are authorised to test. Fingerprint is read-only GET. Confirm is a sleep-only probe, and only after the version flag.

Outputs

• results.jsonl. One row per host: URL, whether Metabase was detected, the version read, the affected flag, and whether the sleep confirm succeeded.
• summary.json. Counts across the list: targets, product hits, affected, and errors.

Integrations

• HTTP. Unauthenticated GET to the product root and /api/session/properties. Confirm is a sleep-only POST on flagged hosts.

Sample output

The records below are illustrative and do not come from a real run. They show one Metabase host inside the CVE-2026-72898 range, one patched host, and one host that is not the product.

{"cve": "CVE-2026-72898", "total_targets": 3, "affected": 1, "not_affected": 1, "errors": 1}

FAQ

Which Metabase versions does this flag?

OSS 0.58.x through 0.63.4 and EE 1.58.x through 1.63.4 on the trains the graph encodes. 0.63.5 / 1.63.5 and later on those lines is the floor the graph treats as not affected. The compare uses the version the product itself served.

Does a flagged host mean CVE-2026-72898 was exploited?

No. A flagged row is patch-lag against the range table. Confirm only asks the server to sleep. Treat a confirmed row as evidence the injection still answers, not as proof someone already used it.

Is this check safe on production?

Yes. Fingerprint is read-only GET. Confirm is a sleep-only probe, only on hosts already in range. It does not dump rows, write data, or create accounts.

Does the check need credentials?

No. It fingerprints the public page and reads /api/session/properties the way an external scanner would.

What is CVE-2026-72898?

SQL injection in Metabase. CISA listed it on KEV. OSS and EE trains are both in the range table. This workflow flags by version, then confirms with a sleep-only probe.

Related workflows

• LiteLLM SQLi (CVE-2026-42208). Reach for it when the next SQLi flag is an LLM proxy.
• MOVEit Transfer SQLi (CVE-2023-34362). Reach for it when the next SQLi flag is a file-transfer appliance.
• Exposed Database Scanner. Reach for it when you want unauthenticated database listeners, not a Metabase version.