Skip to content
Lacambra Web Portal Services
← 2026, week by week
Security · Week 32, 3 to 9 August 2026

Metabase zero-day: what a hacked dashboard can reach

A flaw in Metabase let strangers make themselves its administrator and take the keys to every database it read. What that means for self-hosted reporting.

A ground-floor office window lit at night, showing a row of grey filing cabinets to anyone passing on the wet street outside.

On 6 August 2026 Metabase, the dashboard and reporting tool, said attackers had used an unknown flaw against its cloud service. Its advisory describes an SQL injection that needs no login and can make the attacker an administrator, from where they could take the stored credentials for every connected database and read and export whatever those connections reach. Framework, Tally, Kilo Code and n8n then told customers that their data had been reached through it. Copies that offices run on their own servers, from version 58 on, were open to the same attack, and fixing them was up to whoever ran them.

The attacks began before the warning. Kilo Code said the access took place over about four hours on 2 August, four days before it was alerted, according to The Hacker News. Framework said names, email and postal addresses, phone numbers and login IP addresses were reached, but not payment details; Tally, email addresses and password hashes; n8n, 136 customer records. The flaw became CVE-2026-72898, scored 10 out of 10, and CISA added it to its catalogue of exploited vulnerabilities on 11 August with a three-day deadline.

A reporting tool holds the keys

A dashboard has to read the data to draw the chart, so the tool keeps a login for every database it reports on. That makes it one place where the keys to everything it reports on sit together, and the advisory lists the consequences in that order: administrator access, then the stored credentials, then any data those connections can read. Whatever the dashboard's login can read, a stranger who takes over the tool can read too. Its rights, more than the tool, decide how big a breach is.

Who can reach the login page

The flaw needed no password, only a route to the tool over the network. Wiz, a cloud security firm, found that about a quarter of the self-hosted Metabase instances in the cloud environments it sees were fully reachable from the internet, and saw about 2,500 instances listed by Shodan, a search engine for connected devices. Public exploit code was out by 10 August. Metabase had patched its own cloud by the time it published the warning; a copy on an office's own server stayed open until someone there upgraded it.

A reporting tool is usually for a handful of staff. There is rarely a reason for the rest of the internet to reach its login page.

What it means for the systems I build

Dashboards are on my record. Built or bought, I would hold any of them to two rules. The reporting side reads through its own account, limited to the tables and columns the reports need and unable to change anything, so a takeover stops at what the reports show. And it sits where staff can reach it and strangers cannot, behind the office's single sign-on or VPN rather than on an open address.

Section 20 of the Data Privacy Act of 2012 (Republic Act 10173) is the reason to bother. The organisation that controls personal data must take reasonable measures to protect it against accidental or unlawful disclosure, and a reporting tool that can read staff or customer records falls inside that duty.

Five checks for a self-hosted reporting tool

  • Find every one, including the copy a contractor set up for a single project, and check its version. Metabase's fixes were 58.24, 59.21, 60.17, 61.11, 62.9 and 63.5.
  • Take it off the open internet. Staff can reach it through the VPN or single sign-on; nobody else needs the login page.
  • Give it read-only database accounts limited to what the reports use, never the main application's own account.
  • After any incident at a reporting vendor, change the database passwords the tool held, and check the database logs for queries the reports would never make. Metabase advised both.
  • Ask whoever runs it to search the logs for the pattern Metabase published: a failed password-reset request followed by a successful request for the current user, which Metabase says likely means the instance was compromised.

If nobody can say what your reporting tool can read, or who can reach it, the fit check is where to start.

Sources

  1. Metabase, Security update available for Metabase: Please upgrade now, 6 August 2026
  2. Metabase, on GitHub, SQL injection using an unauthenticated endpoint leading to admin access, 6 August 2026
  3. Help Net Security, Metabase zero-day exploited to access Framework customer data, 10 August 2026
  4. The Hacker News, Metabase Zero-Day Exploited in Wild Allows Admin Access Without Authentication, 8 August 2026
  5. Wiz, Inside the Metabase SQLi: Exploited in the Wild, 10 August 2026
  6. Cybersecurity and Infrastructure Security Agency, Known Exploited Vulnerabilities Catalog
  7. Lawphil, Republic Act No. 10173

Enrique Lacambra III builds internal business systems from Cainta, Rizal.

Email me← All writing

Tell me what is broken and I will tell you if it is worth building. A 20-minute call, no charge, and I will say so if you do not need me.