How widespread is the recent Metabase SQL injection attack?
Source Reddit Cybersecurity
Exploited in the wild · KEV due 14 Aug 2026 · public detection template (Nuclei) : apply the vendor's fix or mitigations to Metabase now.
Data as of 14 Nov 2026, 20:44 UTC
- KEV deadline
- US federal agencies must patch by this date; a sensible deadline for everyone else. Other KEV due dates
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 10 Aug 2026
Detectable: evidence found.
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 1 day after disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
Timeline
CVE published
on cve.org
, t = 0
Added to CISA KEV (opens in a new tab)
exploitation confirmed
, 1 day after disclosure
In Threat Radar
record ingested
, 30 hours after disclosure
KEV remediation due
US federal deadline
, 4 days after disclosure
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MetabaseMetabase | Affected
| Fixed in– |
AI-suggested
A patch fixing this vulnerability is available in Metabase versions after 1.58. Organizations should immediately upgrade to a fixed version (at least 1.58.24 or later) to remediate the issue. The patch validates the user-id parameter to prevent SQL Injection. Self-hosted Metabase instances must be patched as soon as possible. Users should review their /api/session/properties endpoint to identify vulnerable versions and investigate any suspicious activity related to the reset_password API. The vendor advisory and Wiz Threat Intel Center provide detailed remediation and detection guidance. No indication exists that the vulnerability is mitigated without patching. There is no mention of cloud service remediation, so self-hosted instances require manual patching.
Discussion
A zero-day SQL Injection vulnerability (CVE-2026-72898) was disclosed in the Metabase platform on August 6, 2026. The flaw exists in the /api/session/reset_password endpoint, allowing injection via an unexpected user-id parameter in the JSON body. The vulnerability affects versions starting from 1.58 due to a refactor in the auth_identity module. Exploitation has been observed in the wild, with proof-of-concept exploits publicly available. Self-hosted Metabase instances are at risk and should be patched immediately. The patch validates the user-id as a positive integer, preventing injection. The vulnerability impacts multiple database backends supported by Metabase. Organizations with internet-facing Metabase instances should urgently verify and remediate exposure.
r/cybersecurity (opens in a new tab)u/Razin_misab0 points0 comments
I recently led an incident response investigation for a FinTech client involving the exploitation of Metabase, and the impact was significant.
With the recent reports of active exploitation, I'm curious to understand how widespread this is across the security community.
For those working with Metabase:
Has your organization been affected or received a security notification?
Was your Metabase instance internet-facing?
Have you identified exploitation attempts or unauthorized access?
Were you able to patch before exploitation?
Have you observed any data exposure or compromise?
I’m particularly interested in hearing from security teams and Metabase administrators about how many organizations have been affected or potentially exposed.
https://www.wiz.io/blog/inside-the-metabase-sqli-exploited-in-the-wild
If you've investigated a related incident, what did you observe?