Metabase CVE-2026-72898 SQL Injection: Recap and next steps. Rotem Natan Aug 15, 2026 | 6 Minutes Key takeaways. * Metabase disclosed CVE-2026-72898, an unauthenticated SQL injection vulnerability (CVSS 10.0) that attackers were already exploiting in the wild before a patch existed. * A successful attack grants full admin access, exposing connected database credentials, query access, and configuration control - no login required. * Framework and Tally have both disclosed data theft tied to this exact flaw, so the risk is confirmed, not theoretical. * A patch closes the vulnerability going forward, but it doesn't tell you whether an attacker already got in before you patched - check logs, not just version numbers. * Metabase is an application, not a hardened base image - but running it on a hardened container image shrinks what an attacker can do once inside, which is a different layer of defense than patching the app itself. What happened. Metabase disclosed a previously unknown SQL injection vulnerability, tracked as CVE-2026-72898 (also referenced as GHSA-vwf4-m7j8-wcjf), that attackers had already been exploiting in the wild. The flaw is unauthenticated, rated CVSS 10.0, and can let a remote attacker gain full admin access to a Metabase instance - no credentials, no user interaction, just a crafted request to the public password-reset endpoint. It affects Metabase versions x.58.0 through x.63.4. Fixed versions are: * x.58.x | upgrade to x.58.23 or later * x.59.x | upgrade to x.59.21 or later * x.60.x | upgrade to x.60.17 or later * x.61.x | upgrade to x.61.11 or later * x.62.x | upgrade to x.62.9 or later * x.63.x | upgrade to x.63.5 or later From there, an attacker could: * Access connected database credentials * Query accessible data * Change configurations * Export data This isn't theoretical. Both Framework and Tally have disclosed data theft following compromises of their Metabase environments, and n8n disclosed a related breach tied to its own Metabase instance. If you're self-hosting Metabase, act now. Metabase's own recommendations are direct: * Upgrade immediately to the latest patched release for your version. * Revoke all active user sessions. * Review API keys and admin accounts for unexpected changes. * Rotate credentials for every connected database. * Review warehouse logs, Metabase activity, and query history for suspicious access. If you're on Metabase Cloud, Metabase says you're already patched - but that doesn't mean you weren't affected before the patch shipped. The indicator worth checking right now. One sequence in your logs is a strong signal of exploitation: POST /api/session/reset_password | 400 followed by GET /api/user/current | 200 A failed password-reset request immediately followed by a successful "current user" check is consistent with an attacker using the injection to mint themselves a valid session. If you see this pattern, treat the instance as compromised and start incident response - don't wait for further confirmation. The important part: a patch closes the vulnerability, but it doesn't tell you whether someone got there before you patched. Patching and forensic review are two separate steps, and skipping the second one leaves you blind to whether you're cleaning up after an intrusion that already happened. Is Metabase a base image? No - and that distinction matters. It's worth being precise here, because the terminology gets confused: Metabase is an application - an open-source business intelligence and analytics tool. It is not a base image. A base image is the underlying operating system layer a container is built from - things like Debian, Alpine, or a distroless image. When you run Metabase in a container, that container has two layers: the Metabase application code (where this SQL injection lives) and the base image underneath it (the OS, libraries, and runtime Metabase sits on top of). This vulnerability is entirely in the application layer. No base image, hardened or not, would have patched Metabase's password-reset endpoint - that fix has to come from Metabase itself. But the base image layer still matters here, for a specific reason: it determines what an attacker can do once they're in. An attacker who gains admin access to Metabase through this flaw is now operating inside a running container. Whether that container gives them a shell, a package manager, and a path to pivot further, or whether it's stripped down to exactly what Metabase needs to run, depends entirely on the base image underneath it. Why a hardened base image still reduces your exposure. A hardened container image - one stripped of unnecessary components, built with tight default configurations, and continuously scanned and patched - doesn't stop an application-layer SQL injection. What it does is limit the blast radius if an attacker gets in through one: * No shell or package manager in production images means an attacker with admin access to Metabase has a much harder time pivoting into the underlying host or pulling in additional tooling. * A minimal attack surface means fewer binaries and libraries are present to exploit for privilege escalation or persistence, even after initial compromise. * Continuous rebuilds and fast CVE remediation at the OS layer mean the environment Metabase runs in isn't independently exposing you to a second, unrelated vulnerability while you're already dealing with this one. This is the same logic behind why teams increasingly run applications - Metabase included - on CVE-free base images rather than default upstream images that ship with thousands of known vulnerabilities baked in before a single line of application code runs. The application still needs patching on its own schedule. The base image is what determines how contained an incident stays if that patching happens a day too late. If you're evaluating how your container foundation holds up independent of application-layer bugs like this one, Echo's guides on container image vulnerability best practices and AI-ready hardened container images cover what a genuinely hardened base layer looks like in practice. Faq. Is Metabase itself a hardened base image? No. Metabase is an application that runs inside a container, typically on top of a base image like Debian or Alpine. A hardened base image refers to that underlying OS layer, not to Metabase's own code. The two are separate layers of the same deployment, and this vulnerability lives entirely in Metabase's application code. Does a hardened base image protect against this SQL injection? Not directly - the flaw is in Metabase's password-reset endpoint, so only a Metabase patch fixes it. A hardened base image reduces what an attacker can do after gaining access, by removing shells, package managers, and unnecessary components that would otherwise help them pivot further inside the container or host. How do I know if I was compromised before I patched? Check your logs for a failed POST /api/session/reset_password request immediately followed by a successful GET /api/user/current request - this is the signature of CVE-2026-72898 being exploited. Also review admin accounts, API keys, and warehouse query logs for unexplained changes or access around the time the vulnerability was disclosed. What's the difference between patching Metabase and hardening the container it runs in? Patching Metabase fixes the specific application vulnerability - in this case, the SQL injection in the password-reset flow. Hardening the container's base image is a separate, ongoing practice that reduces the overall attack surface, so that whatever the next application-layer bug turns out to be, the surrounding environment limits how far an attacker can go. Should self-hosted Metabase users do anything beyond upgrading? Yes. Upgrading closes the vulnerability going forward, but it doesn't undo any access an attacker gained beforehand. Revoke active sessions, rotate all connected database credentials, and audit admin accounts and query logs, since the CVSS 10.0 rating and confirmed in-the-wild exploitation mean this wasn't a low-probability risk.

Metabase sqli zero-day exploited: data theft attacks confirmed. This article was written by a language model from the source above and was not reviewed by a human before publication. Verify anything operational against the original. Editorial policy Key points * " Metabase Cloud and self-hosted instances are compromised via a critical SQL injection zero-day, leading to customer data theft. * " Affected systems include Metabase versions 1.58 and above, including 0.58.x through 0.63.x branches. * " Immediately upgrade self-hosted Metabase instances to patched versions and follow post-compromise remediation steps. A critical, unauthenticated SQL injection zero-day vulnerability in Metabase, affecting versions 1.58 and above, has been actively exploited in the wild, leading to data theft from customer instances. Metabase, a popular open-source business intelligence platform, disclosed the attacks, confirming that its Metabase Cloud SaaS platform was compromised. Self-hosted installations are also vulnerable if not updated, posing a significant risk to organizations utilizing the platform, according to BleepingComputer. Metabase has identified and blocked the attack endpoints, subsequently rolling out a fix for the vulnerability. This unauthenticated SQL injection flaw allows a remote attacker to gain administrator access to a customer's Metabase instance. With administrative control, attackers can alter application configurations, steal stored credentials for connected databases, access any data available through those connections, and export sensitive information. Technical details of the Metabase sqli zero-day vulnerability. The zero-day, described by Metabase as a 'CRITICAL' vulnerability with a CVSS score of 10.0, enables attackers to inject arbitrary SQL into the Metabase application database. This critical flaw grants immediate administrative access without requiring any prior authentication. The broad capabilities afforded by this access include: * Configuration Manipulation: Attackers can modify Metabase application settings. * Credential Theft: Stored credentials for any connected databases can be exfiltrated. * Data Exfiltration: Any data accessible via database connections can be read and exported. The exploitation of this vulnerability has already impacted several organizations. Laptop manufacturer Framework confirmed that its Metabase instance was compromised on August 3, leading to the theft of customer information. This data included full names, email addresses, login IP addresses, billing and shipping address information, phone numbers, and company names. For Framework for Business customers, additional data such as VAT, EIN, and billing email addresses may also have been exposed. Online form builder Tally also reported a compromise of its Metabase analytics environment on August 3. Attackers accessed email addresses and cryptographic hashes of user passwords. Tally clarified that user forms and submitted answers, stored separately, were not affected. LexisNexis, while not explicitly linking its incident to this specific Metabase API vulnerability, confirmed that its Metabase API was impacted by a cyberattack on a third-party vendor earlier this week, causing service disruptions. Metabase states that all its Cloud customers have been automatically upgraded and patched. However, organizations running self-hosted Metabase instances must perform manual updates to secure their systems against this active threat. Mitigation and remediation for Metabase 1.58+ unauthenticated SQL injection. Given the active exploitation and critical nature of this vulnerability, immediate action is paramount for all self-hosted Metabase users. The following steps are crucial for Metabase 1.58+ unauthenticated SQL injection remediation: * Immediate Upgrade: Update all vulnerable Metabase installations to the patched versions. The minimum safe releases are 0.58.24, 0.59.21, 0.60.17, 0.61.11, 0.62.9, and 0.63.5. * Temporary Workaround: If immediate upgrading is not possible, temporarily block access to the /api/session/reset_password endpoint. This serves as a critical, albeit temporary, measure to prevent exploitation. * Post-Compromise Actions: For any potentially compromised instances, Metabase strongly recommends: * Revoking all active user sessions. * Reviewing API keys and administrator accounts for any unauthorized changes. * Rotating credentials for all connected databases. * Inspecting application logs and query history for signs of compromise. How to detect Metabase data theft compromise. Organizations should actively look for indicators of compromise (IOCs) in their system logs to detect Metabase data theft compromise. Attacks can be identified by a POST request to /api/session/reset_password returning a 400 status code, immediately followed by a successful GET request to /api/user/current. The presence of these entries in system logs strongly suggests that an instance has been compromised, and a full forensic investigation should be initiated immediately.

Framework data breach exposes customer information via vendor. technology TrendPulse AI Analysis This article covers technology trends, sourced from TechCrunch. Its AI system has analyzed the key points and extracted the most relevant insights for decision-makers. Below is the structured breakdown of the original content. Quick summary. * Modular laptop manufacturer Framework has confirmed a data breach affecting its entire customer base, resulting in the theft of names, email addresses, phone numbers, and physical addresses. * The incident originated from a supply chain attack on Metabase, a business intelligence provider, which suffered a zero-day exploit that allowed unauthorized access to cloud-hosted databases. * While personal contact information was compromised, the company confirmed that no customer payment data or financial records were accessed during the breach. Key details. Framework, known for its focus on repairability and modular hardware, recently alerted its user base to a significant security incident. According to company spokesperson Eric Schumacher, the breach impacted all customers, though the firm has not disclosed the exact number of individuals affected. While the company occupies a niche segment of the PC market, industry estimates suggest the user base spans hundreds of thousands of device owners. The breach was not a direct attack on Framework's own infrastructure but rather a downstream consequence of a security failure at Metabase. Metabase publicly disclosed that attackers utilized an unknown security flaw - a zero-day vulnerability - to bypass protections and gain access to customer databases stored on their cloud servers. Framework's internal investigation confirmed that while their cloud instance was accessed, sensitive financial data remained secure. The hackers exploited the bug to give them the ability to access customers' databases stored on Metabase's cloud servers. Why this matters. This incident highlights the growing fragility of the modern software supply chain. Even companies with strong internal security protocols remain vulnerable to the weaknesses of their third-party vendors. For executives and IT decision-makers, this serves as a stark reminder that vendor risk management is no longer a secondary concern but a critical component of an organization's overall cybersecurity posture. As businesses increasingly rely on specialized SaaS tools for business intelligence and data analytics, the attack surface expands significantly. Organizations must prioritize rigorous vendor auditing and demand transparency regarding the security practices of their partners. Moving forward, companies should adopt a 'zero-trust' approach to third-party integrations, ensuring that even if a vendor is compromised, the blast radius of the stolen data is strictly limited. The bottom line. The Framework breach underscores the urgent need for companies to treat third-party vendor security as a core extension of their own internal risk management strategy. This article has been processed and analyzed by TrendPulse AI for informational purposes. Content may have been summarized or restructured for clarity.