MediumVulnerabilityMonitoring

HIPAA Journal reports Metabase zero-day behind Dorsata breach

HIPAA Journal reports Dorsata says a Metabase zero-day exposed data of 58,249 people; Metabase users should confirm they are patched.

Published
Fixed in
Patch applied by Dorsata, fixed Metabase version not confirmed
Exploitation
Yes, according to Dorsata’s account as reported by HIPAA Journal; no independent verification and no CVE confirmed

What happened

According to the HIPAA Journal, Dorsata, Inc., an Arlington, Virginia healthcare technology company, has disclosed a data breach to the HHS Office for Civil Rights involving the protected health information of 58,249 individuals. The HIPAA Journal reports that Dorsata uses Metabase business intelligence software and was informed on or around August 12, 2026 that Metabase contained a previously unknown (zero-day) vulnerability. The outlet says a patch was applied and cybersecurity experts were engaged to check whether the flaw had been exploited before patching.

The HIPAA Journal says the investigation confirmed that between August 10, 2026 and August 12, 2026, an unauthorized third party exploited the vulnerability and accessed a database platform holding medical information related to patients of Dorsata’s healthcare provider partners. Per the outlet, the affected data included names, addresses, patient IDs, dates of birth, vitals data, treatment information, treatment locations, provider names, vaccination information, medications, health insurance information, and medical histories.

The HIPAA Journal also reports that no evidence was found that the information has been misused. It says the group behind the initial exploitation has not been established, but that the Dire Wolf group appears to have exploited the vulnerability in at least two subsequent attacks, according to VenariX (as relayed by the HIPAA Journal).

What is not confirmed: a CVE identifier, the affected and fixed Metabase versions, how many other organizations were affected, and any independent verification of Dorsata’s account. The only source here is the HIPAA Journal’s report. We have not seen Dorsata’s own notice or a Metabase advisory.

The same HIPAA Journal article covers two unrelated incidents, at Bay Area Psychological Consultants and Lansing Urgent Care. The outlet does not link either to Metabase.

Am I affected?

  • Metabase users: possibly. The source does not say which Metabase versions were vulnerable or which are fixed, so the affected range is not confirmed.
  • Patients of Dorsata’s provider partners: the HIPAA Journal says the exposed database held their records. The source does not say whether or how affected individuals will be notified.
  • Everyone else: the source gives no basis for concern outside Metabase deployments and Dorsata-related data.

What to do now

The source contains no remediation guidance beyond Dorsata applying a patch. The steps below are our editorial suggestions, not sourced claims.

  1. Check Metabase’s own security advisories and release notes for this vulnerability and the fixed version, since the HIPAA Journal does not name them.
  2. Update any Metabase instance you operate to the patched release once you have confirmed it.
  3. Review access logs for your Metabase instance and its connected databases around August 10 to 12, 2026, the window the HIPAA Journal reports for the exploitation.
  4. If you are a Dorsata provider partner, contact Dorsata directly for details, as the source does not say what notification is planned.

Sources