Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2026-72898: Unauthenticated SQL Injection in Metabase Password-Reset API

Published Aug 10, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days6 mentions · peak 2 in a dayToday
CVSS10.0Critical · v4
EPSS98.5%100th percentile
CISA KEVYesAdded Aug 11, 2026
In the wildActivePer CISA KEV
Vendor
Metabase
IdentifiersCVE-2026-72898CWE-89 · Improper Neutralization of Special…

CVE-2026-72898 is a critical unauthenticated blind SQL injection vulnerability in Metabase's password-reset API. Vulnerable authentication processing merges request data with authentication results, retaining an attacker-controlled user-id value when authentication does not supply one. A structured user-id containing HoneySQL's :raw directive subsequently reaches a t2/select-one query and is interpreted as literal SQL rather than parameterized input. This permits arbitrary SQL execution against Metabase's application database and can provide administrator access. The vulnerability affects unpatched Open Source 0.58–0.63 branches and corresponding Enterprise 1.x branches; releases before branch 58 are unaffected. The fix validates that user-id is a positive integer before querying. Metabase disclosed the vulnerability on August 6, 2026, following zero-day exploitation against Metabase Cloud.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can compromise Metabase application data and administrator accounts, exposing saved queries, configuration, API keys, and credentials for connected databases. Attackers can read or export accessible business data and potentially modify application state or disrupt service. Observed exploitation included unauthorized administrator creation, data theft, and extortion. Operating-system command execution is possible in deployments with sufficiently privileged database connections, including PostgreSQL connections permitted to execute server-side programs; this is a conditional downstream consequence, not an inherent outcome on every installation.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrading is impossible, temporarily block access to /api/session/reset_password. Restrict Metabase network accessibility to authorized users and remove unnecessary public exposure. Apply least privilege to application-database and connected-database accounts; PostgreSQL accounts should not have superuser access or unnecessary pg_execute_server_program privileges. Monitor for suspicious password-reset requests, unexpected administrator accounts, API keys, sessions, database-connection changes, unusual queries, exports, and server processes spawning shells.

Remediation

Patch, then assume compromise.

Upgrade immediately to the latest supported Metabase release. Initial fixes for this CVE were Open Source versions 0.58.24, 0.59.21, 0.60.17, 0.61.11, 0.62.9, and 0.63.5, with corresponding Enterprise versions using the 1.x prefix. Subsequent security guidance raised minimum safe releases to 0.58.31, 0.59.28, 0.60.24, 0.61.18, 0.62.16, and 0.63.13, respectively, or their Enterprise equivalents, to address additional vulnerabilities. For previously exposed installations, revoke active sessions, investigate administrator changes and unrecognized API keys, rotate connected-database credentials, and review Metabase activity, query history, and database or warehouse logs. Patching alone does not remove access already established by an attacker.

Public exploits

Exploits

7 exploits validated by Mallory's analysis. Hidden: 5 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
CVE-2026-72898This five-file repository contains an operational Python proof of concept and a self-contained Docker laboratory for the claimed CVE-2026-72898 Metabase password-reset SQL injection. metabase_exploit.py is the primary entry point: it POSTs a JSON user-id object with a raw SQL fragment to /api/session/reset_password, ignores the expected HTTP 400 response, and uses response latency as a PostgreSQL pg_sleep-based blind SQL oracle. It randomizes X-Forwarded-For for every request to evade a per-source reset-password throttle where the deployment trusts that header. The extractor supports a check-only mode, custom scalar SQL expressions, configurable delay, and optional disabled TLS verification; its default expression reads the earliest core_user email. The supporting Dockerfile, start.sh, and setup_bg.sh construct a reproducible vulnerable environment using metabase/metabase:v0.62.1 and a localhost PostgreSQL application database. start.sh initializes PostgreSQL, creates the mb role and metabase database, and launches Metabase. setup_bg.sh polls the local session-properties endpoint, retrieves the setup token, and invokes /api/setup to create a randomized-password admin account (admin@lab.local), ensuring the container reaches the login state. The README documents affected and patched version ranges, container startup, extraction examples, and mitigation guidance. No external command-and-control or hard-coded remote attacker infrastructure is present; the only remote target is operator supplied.EQSTLab · Disclosed Aug 27, 2026 · python · bash · webOperationalCVE-2026-72898This nine-file repository is a standalone, loopback-restricted exploitation lab, not a framework module or detection-only tool. It attributes a password-reset SQL injection to CVE-2026-72898: an unexpected user-id field allegedly reaches a raw SQL expression in the Metabase application database, enabling temporary administrator-session creation. The CVE attribution and actual injection expression cannot be independently confirmed from the supplied material because the central portion of exp.py is truncated. The visible Python code validates the Compose project, expected image, loopback binding, running service, initial superuser, and synthetic order state. It sends HTTP requests with optional X-Metabase-Session authentication. The visible final stage exports synthetic data, deletes order 105, verifies the deletion, revokes the temporary session, and checks that subsequent authentication returns HTTP 401. Export and deletion are post-authentication actions against a connected analytics database, not direct password-reset injection into that database. Deletion depends on the analytics_reader account's deliberately granted DELETE permission. No reverse shell, external collection endpoint, or arbitrary command-execution payload is visible. compose.yaml defines five services: vulnerable Metabase v0.63.2, patched comparison v0.63.18.3, separate PostgreSQL application databases, and a shared PostgreSQL 16 analytics database. data/01-seed.sh and data/02-seed.sql initialize four customers, five orders, a separate private contact table, and the analytics_reader role. That role receives analytics-schema access but no explicit access to the private schema. start.ps1 creates random credentials and starts selected profiles; verify.ps1 checks HTTP health and synthetic row counts. recover.py restores order 105 through local Docker/database access and removes only recognized export files after containment and header checks. README.md documents setup and comparison, while .gitignore excludes credentials and exports. Six files contain executable or SQL code, covering Python, PowerShell, shell, and SQL. The evidence supports a basic operational lab exploit with fixed follow-on actions, although its success was not tested. The repository URL, analyzed Git reference, and archive size were not supplied; empty metadata strings and size 0 indicate unavailable information.amier-ge · Disclosed Oct 4, 2026 · python · powershell · webOperationalmetabase-cve-2026-72898The repository contains nine files: two executable Python utilities, a static HTML/CSS publication, four Markdown research/transcript documents, .gitignore, and a GitHub Pages .nojekyll marker. It is standalone exploit research rather than a framework module. The main exploit, poc/poc_takeover.py, performs active version and endpoint checks, then attempts two unauthenticated takeover chains. An extra user-id JSON object reaches a HoneySQL raw-SQL form through the password-reset authentication flow. Phase A uses stacked SQL to insert a core_session row for user_id=1, hashing an attacker-generated UUID with SHA-512, then supplies that UUID in the metabase.SESSION cookie. Phase B overwrites the configured administrator's bcrypt password hash and salt, logs in, checks the current user's superuser status, and requests /api/database. The accompanying transcript reports successful administrator access after injection requests returned HTTP 400. These results are supplied evidence, not independently executed or verified here. The exploit is operational but brittle: its target URL, administrator email, user ID, session-row ID, and replacement password are hardcoded; it does not enforce a vulnerable-version check or gate later destructive actions on earlier success. Phase B changes existing credentials, and neither chain includes cleanup. An HTTP 400 exposure check alone is not proof of SQL injection. The initial GET is active reconnaissance, notwithstanding its passive label. recon/shodan_metabase_recon.py is a separate passive exposure-enumeration utility that contacts Shodan rather than candidate Metabase hosts. It supports custom queries, tagged outputs, key rotation, and resume behavior, then exports JSONL, CSV, and summary files. Deduplication uses IP alone, potentially collapsing distinct services on different ports. The key-file permissions and exclusion claimed in its docstring are not enforced by the supplied code or .gitignore. The documentation additionally describes user-data.email account-selection abuse, orphan session creation, timing/user-enumeration oracles, arbitrary SQL, and H2 file-write/Java-execution possibilities. Those broader capabilities are not implemented in the supplied Python PoC. The lab report's early inability to acquire orphan-session keys is superseded by later raw-SQL session-forgery findings. The text reports fixes in 0.63.5/1.63.5, while also reporting rejection in 0.62.9; consequently, a blanket claim that all versions below 0.63.5 are vulnerable should not replace branch-specific version assessment. CVE, exploitation-in-the-wild, exposure counts, and vendor-fix claims remain repository assertions without external corroboration in this analysis. LAB-VALIDATION.md and docs/index.html are truncated in the supplied content. No archive metadata or analyzed Git reference was provided; size_bytes=0 denotes unavailable archive size, and ref is left blank. The listed uncompressed file sizes total 74,224 bytes.Riftweld · Disclosed Oct 12, 2026 · python · html · web · networkOperationalCVE-2026-72898-metabaseThe repository contains two standalone Python CLI tools, a README, and a .gitignore. The checker is described as combining reachability, Metabase identification, static version ranges, and SQL-error indicators, with single-target or target-file input and JSON reporting. Its visible code configures requests retry handling and database-error pattern matching. The active PoC constructs a concrete SQL payload intended to insert an administrator session into core_session through the unauthenticated reset-password endpoint, then verifies the session through /api/user/current. It supports target lists and TSV output and prints session credentials and administrator email on success. Despite its 'non-destructive' docstring, the payload writes database state. TLS certificate verification is disabled globally in the PoC, and reports or verbose logs can expose sensitive session data. No exploit framework, command execution payload, fixed external callback, or exfiltration destination is evident. The checker hardcodes claimed fixed versions 0.58.24, 0.59.21, 0.60.17, 0.61.11, 0.62.9, and 0.63.5; neither those claims nor the CVE's validity can be established from the supplied material. Both Python files are truncated, limiting verification of request handling, session presentation, and detection logic. There is no visible evidence of malicious behavior against the operator, but successful exploitation is not demonstrated. Repository URL, git reference, and archive size were not supplied; the four listed file sizes total 44,822 bytes, which is not an archive-size measurement.gagaltotal · Disclosed Oct 13, 2026 · python · webOperationalmetapwn-massThe supplied repository listing contains README.md (12,057 bytes) and a standalone Python entry point, metapwn.py (35,844 bytes). Both displayed files are truncated. The repository URL is inferred from the README installation command; no git reference or archive size was provided. size_bytes is therefore recorded as 0 to indicate unavailable metadata, not an empty repository. The visible code implements standard-library HTTP helpers, JSON requests, randomized X-Forwarded-For values, thread-safe TSV output, target-list processing, and a queue-based worker launcher. It defines password-reset and current-user API paths, candidate web roots, and a default 'id' command. Despite a Python-version compatibility branch, unconditional Queue and urllib2 imports prevent ordinary Python 3 execution. The README attributes the attack to CVE-2026-72898 and describes password-reset SQL injection leading to forged privileged sessions. Its claimed PostgreSQL chain uses a probe account's last_name as a read-back channel, pg_sleep for engine detection, role enumeration, COPY TO/FROM PROGRAM or archive_command for command execution, pg_read_file for reads, and lo_export or COPY for writes. Additional advertised functions include account creation, administrator password reset, optional password-hash collection, environment and .pgpass extraction, PHP web-shell placement, and cleanup. These are potentially state-changing exploitation features, not merely vulnerability detection. The central injection, privilege probing, command execution, shell deployment, and cleanup implementations are absent from the supplied excerpt. Consequently, the CVE attribution, affected versions, exploit validity, and advertised capabilities cannot be independently confirmed. No visible evidence establishes that this is a fake exploit, but the classification reflects its intended purpose rather than demonstrated success. Altering archive_command, creating accounts, or writing files could leave persistent changes; advertised cleanup cannot be verified. No hardcoded command-and-control or exfiltration destination is visible. Targets and an optional shell base URL are operator supplied. README example hosts and the GitHub attribution link are not operational callbacks. The generated IPv4 strings appear only in X-Forwarded-For headers, not as connection targets. The code also defines NON_WEB_PORTS containing 5432, 5433, 3306, 6379, 27017, 9200, and 11211, but their actual use is omitted.Jenderal92 · Disclosed Nov 12, 2026 · python · web · networkOperationalCVE-2026-72898Repository contains two files: a README and a single Python exploit script, cve-2026-72898_poc.py. The script is a standalone operational PoC for CVE-2026-72898, an unauthenticated SQL injection in Metabase's password-reset workflow. It is not part of a larger exploit framework. Exploit flow is three-step: (1) GET the target root path / and require HTTP 200, (2) POST crafted JSON to /api/session/reset_password with a malicious user-id.select.raw value containing SQL that inserts a forged admin session row into core_session using a generated UUID and its SHA-256 hash, and (3) send the forged session via X-Metabase-Session to /api/user/current to verify administrator access. If the final request returns HTTP 200 with JSON, the script marks the target vulnerable and prints the forged session ID and admin email. The exploit's main capability is admin takeover without credentials. It does not deploy a shell or arbitrary post-exploitation payload; instead it creates an authenticated Metabase superuser session that can be reused in the browser through the metabase.SESSION cookie. The README documents both single-target and mass-target usage, expected response patterns, and manual browser steps for converting the forged session into full UI access. Code structure is simple: helper functions for colored output, session creation, SQLi body construction, target checking, and CLI parsing. It supports reading targets from a file, configurable timeout, and optional TSV output. The payload is hardcoded and purpose-built for session forgery, making the repository an operational exploit rather than a mere detector.4minx · Disclosed Aug 15, 2026 · markdown · python · web · networkPoCCVE-2026-72898This repository is a minimal proof-of-concept exploit consisting of a short README and a single Bash script, poc.sh. The script uses curl to send an HTTP POST request to a local web application's password reset endpoint at /api/session/reset_password. The JSON body includes a token, a replacement password, and a nested user-id.raw field containing the SQL injection string "1) OR 1=1 -- ". The apparent goal is to exploit insufficient input sanitization in backend password reset logic, likely causing the reset operation to match unintended users or bypass intended constraints. The exploit is operational but basic: it contains a hardcoded target URL, hardcoded password, and hardcoded injection payload, with no automation, validation, or framework integration. The README provides no meaningful technical guidance.VuxNx · Disclosed Aug 15, 2026 · bash · webPoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
MetabaseMetabaseapplication
FAQ

Frequently asked questions

Is CVE-2026-72898 exploited in the wild?
Yes. As of Nov 17, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Aug 11, 2026.
Is there a public exploit for CVE-2026-72898?
Yes. Mallory tracks 7 public exploits or proofs of concept for CVE-2026-72898, the earliest disclosed Aug 15, 2026.
Is there a patch for CVE-2026-72898?
Upgrade immediately to the latest supported Metabase release. Initial fixes for this CVE were Open Source versions 0.58.24, 0.59.21, 0.60.17, 0.61.11, 0.62.9, and 0.63.5, with corresponding Enterprise versions using the 1.x prefix.
What products are affected by CVE-2026-72898?
Metabase.
How severe is CVE-2026-72898?
CVE-2026-72898 has a CVSS v4 score of 10.0 (Critical) and an EPSS score of 98.5% (100th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

141 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
medium xpl0decNews · Nov 17, 2026Metabase SQL Injection & UAF. Beberapa waktu lalu saya sempat membuat… | by xpl0dec | Nov, 2026 | MediumThe article describes an unauthenticated SQL injection vulnerability affecting Metabase Open Source versions before 0.58.24. An attacker-controlled user-id map containing a raw expression reaches a database query through HoneySQL. In the author's challenge environment, exploitation enables remote command execution through PostgreSQL COPY TO PROGRAM when the database account has sufficient privileges. The demonstrated subsequent escalation to root relies on a separate, unnamed use-after-free vulnerability in a challenge binary, not on this CVE alone.Read more ↗malware newsNews · Nov 6, 2026October 2026 CVE Landscape - Malware Analysis - Malware Analysis, News and IndicatorsA Metabase vulnerability reported as actively exploited in October 2026.Read more ↗levelblue spiderlabs blogNews · Oct 28, 2026LevelBlue TTP Briefing Q3 2026: Trusted Access Fuels Data TheftAn unauthenticated SQL injection vulnerability in Metabase, described as having a CVSS score of 10 and potentially enabling remote code execution and account takeover with administrator access. Observed exploitation provided a complete intrusion path through administrator account creation, access to connected third parties, data theft, and extortion.Read more ↗mbsd blogNews · Oct 19, 20262026年9月度 MBSD-SOCの検知傾向トピックス | 技術者ブログ | 三井物産セキュアディレクション株式会社A critical SQL injection vulnerability in Metabase's unauthenticated /api/session/reset_password endpoint that can allow authentication bypass and administrator access. The report assigns a CVSS v3.0 score of 10.0 and states that public proof-of-concept code is available. MBSD-SOC first detected attacks on August 19, 2026, with increased activity in September. The illustrated request probes whether exploitation is possible; successful compromise is not established. Affected releases are earlier than x.58.24, x.59.21, x.60.17, x.61.11, x.62.9, and x.63.5 within their respective release branches. Updating to the latest version is recommended.Read more ↗
+26 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence4Every report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures3YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity102Community discussion across Reddit, Mastodon, and other social sources.