Skip to content

News

Metabase CVE-2026-72898: how to organise your response

A critical flaw in the Metabase password reset endpoint, CVE-2026-72898, is listed by CISA as exploited. This article explains who is affected and how to organise the response.

  • Published on
Abstract pattern of navy and red shapes on a navy grid: the standard cover of an article about a security advisory.

This article was written automatically on 18 November 2026 from the information on this site and checked by automated rules; it was not reviewed by a person. Tell us if something is wrong

What has been reported

Metabase has reported a SQL injection in the password reset endpoint of its product. SQL injection is a flaw in which input sent to an application is treated as part of a database command. In this case, a remote attacker who is not logged in can use it to gain administrator access.

The issue is tracked as CVE-2026-72898 and was disclosed on 10 August 2026. It has a CVSS score of 10.0, the top of the scale, and its severity is critical. CISA, the United States cybersecurity agency, lists it as exploited. That is a good reason to act promptly and in an organised way.

The technical details are on the PiLabs advisory for CVE-2026-72898, which is a summary of public sources. This article does not add technical detail. It focuses on what a manager needs to organise.

Which versions are affected

The advisory lists these ranges of Metabase. A version is affected if it falls inside one of them:

  • 0.58.0 up to, but not including, 0.58.24
  • 0.59.0 up to, but not including, 0.59.21
  • 0.60.0 up to, but not including, 0.60.17
  • 0.61.0 up to, but not including, 0.61.11
  • 0.62.0 up to, but not including, 0.62.9
  • 0.63.0 up to, but not including, 0.63.5
  • 1.58.0 up to, but not including, 1.58.24
  • 1.59.0 up to, but not including, 1.59.21

The Metabase security advisory on GitHub lists the fixed releases. Use it as the final word, not a summary.

Why it matters to your organisation

Metabase is a tool for reports and dashboards. It is usually connected to company databases so that people can look at data without writing queries. Administrator access to such a tool may give an attacker a view of those connections and of the data behind them. How far that goes depends on how your instance is set up, so it needs to be checked and not assumed.

The password reset function is used before anyone logs in. An endpoint like that can be reached by people who have no account. This is why the flaw does not depend on a stolen password.

How to organise the response

  1. Find out whether you run Metabase. Reporting tools are often installed by a single team and forgotten by everyone else. Ask the IT, data and business teams. If a supplier hosts it for you, ask them.
  2. Check the version. Compare the version in use with the ranges above.
  3. Read the vendor instructions. The Metabase advisory lists fixed releases and explains how to check whether your instance is exposed. The vendor also publishes a security update post.
  4. Reduce exposure while you prepare. If it does not break business use, limit who can reach the instance from the internet.
  5. Update. Take a backup first, then update to a fixed release, and test that reports still work. Agree a short maintenance window with the people who rely on the dashboards.
  6. Look back. Because exploitation has been reported, review the administrator accounts and the access logs for anything unexpected. Consider whether the database credentials stored in the instance should be changed.
  7. Decide on the fallback. CISA's required action is to apply mitigations according to vendor instructions, or to stop using the product if mitigations are not available.

Questions worth asking

To your own IT team:

  • Which Metabase instances exist, and who owns each one?
  • Which version does each run, and can it be reached from the internet?
  • Which databases are connected, and what data do they hold?

To a supplier that runs it for you:

  • Which version do you run for us, and when will it be updated?
  • Have you checked for signs of misuse since the disclosure?
  • Will you confirm in writing when the work is finished?

Keep the answers in one place. They will help with the review afterwards and with any later advisory for the same product.

Support from Pinet

Pinet offers cybersecurity consulting, and its PiLabs section publishes summaries of security advisories such as this one. The full summary for this issue is on the PiLabs advisory page for CVE-2026-72898.

More

More news

All news

How to choose a firewall size for a branch office

A firewall that is too small slows the branch down, and one that is too large wastes budget. This guide explains what to measure and what to ask before you choose.

Have a question about this news?

Write to us. A consultant will answer.