<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/august-2026-security-vulnerability-what-happened--vf4dqe4hg" -->

---
title: August 2026 Security Vulnerability: What happened?
description: A detailed postmortem explains a critical zero-day chained SQL injection vulnerability in Metabase, exploited via the /reset-password endpoint. The root cause...
canonical: https://daily.dev/posts/august-2026-security-vulnerability-what-happened--vf4dqe4hg
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: August 2026 Security Vulnerability: What happened? | daily.dev
og:description: A detailed postmortem explains a critical zero-day chained SQL injection vulnerability in Metabase, exploited via the /reset-password endpoint. The root cause...
og:url: https://daily.dev/posts/august-2026-security-vulnerability-what-happened--vf4dqe4hg
og:image: https://api.daily.dev/og/posts/vF4DqE4HG.png
og:image:alt: August 2026 Security Vulnerability: What happened?
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# August 2026 Security Vulnerability: What happened?

**[Metabase](https://daily.dev/sources/metabase)** · 4 min read · 6 upvotes · 1 comments

## Summary

A detailed postmortem explains a critical zero-day chained SQL injection vulnerability in Metabase, exploited via the /reset-password endpoint. The root cause spanned four layers: unclosed Malli type annotations that allowed extra keys, a November 2025 auth refactor that began passing the full request body, a user lookup by raw ID through the Toucan2 ORM, and HoneySQL's handling of a 'raw' key as unescaped SQL. All installations on version 0.58+ were vulnerable; under 3% of cloud customers, plus some self-hosted/open source users with public instances, were compromised before an August 6, 2026 patch. Metabase believes the attack's complexity and reconnaissance (LLM-like user agents such as 'metabase-postgres-admin-session-lab-verifier') indicate it was executed with significant LLM assistance, prompting broader hardening efforts including a version 63.13 release.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.metabase.com/blog/vulnerability-what-happened>

## Questions this post answers

### What was the root cause of the Metabase password reset SQL injection vulnerability disclosed in August 2026?

A chained flaw across four layers: Malli API type annotations did not reject extra keys in the /reset-password request body, an auth refactor from November 11, 2025 began passing the entire body instead of just token and password, the auth flow looked up users by ID via Toucan2's select-one, and HoneySQL treated a 'raw' key in the filter predicate as literal SQL to execute, letting an attacker inject SQL through a crafted user_id parameter.

_Teams running Metabase can track the disclosed attack chain on daily.dev to confirm they're patched._

### Which Metabase versions were affected by the August 2026 zero-day and when was it patched?

All Metabase installations running version 0.58 and later were vulnerable. The vulnerability was discovered after a customer reported an anomalous API key creation on August 3, 2026, and patches were packaged and released on August 6, 2026, with a further hardening release, version 63.13, following shortly after.

_daily.dev helps developers stay on top of urgent patch timelines like this Metabase fix._

### How did attackers exploit the Metabase SQL injection to gain access?

Attackers submitted a password-reset request with a user_id field containing a raw SQL payload such as {"raw": "1);INSERT INTO ...; --"}, which HoneySQL executed literally, inserting a forged session record tied to user ID 1, the default admin account. That session was then used to browse data and create an API key enabling bulk table downloads.

_Understanding real exploit chains like this helps developers harden their own auth flows, something daily.dev readers track closely._

## Community discussion

Top comments from developers on daily.dev.

**@agustinbarrientos** · 0 upvotes

> My regression suite would exercise the four-layer chain against every supported database. Unit tests at each boundary can all pass while their composition stays dangerous. I'd rerun that case on every ORM and query-builder upgrade.

## Similar posts on daily.dev

- [February 2026 vulnerability: What happened?](https://daily.dev/posts/february-2026-vulnerability-what-happened--9s3vxho4x) · Metabase · 1 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security), [#sql](https://daily.dev/tags/sql)

[View this post on daily.dev](https://daily.dev/posts/august-2026-security-vulnerability-what-happened--vf4dqe4hg)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"August 2026 Security Vulnerability: What happened?","url":"https://daily.dev/posts/august-2026-security-vulnerability-what-happened--vf4dqe4hg","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/august-2026-security-vulnerability-what-happened--vf4dqe4hg"},"datePublished":"2026-08-27T23:35:11.480Z","dateModified":"2026-09-13T19:46:30.202Z","description":"A detailed postmortem explains a critical zero-day chained SQL injection vulnerability in Metabase, exploited via the /reset-password endpoint. The root cause...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/18a6848e943e72a157596ae784bc8e95?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/18a6848e943e72a157596ae784bc8e95?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Metabase","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Metabase","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/97c4b2294a914263b4f3b4a82a5f896b","url":"https://daily.dev/sources/metabase"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/august-2026-security-vulnerability-what-happened--vf4dqe4hg","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":6},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"security,sql","timeRequired":"PT4M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Metabase","item":"https://daily.dev/sources/metabase"},{"@type":"ListItem","position":3,"name":"August 2026 Security Vulnerability: What happened?"}]}
{"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/august-2026-security-vulnerability-what-happened--vf4dqe4hg","comment":[{"@type":"Comment","text":"My regression suite would exercise the four-layer chain against every supported database. Unit tests at each boundary can all pass while their composition stays dangerous. I’d rerun that case on every ORM and query-builder upgrade.","datePublished":"2026-08-30T08:28:03.184Z","url":"https://daily.dev/posts/vF4DqE4HG#c-ogX8TfauE","author":{"@type":"Person","name":"Agustin Barrientos","url":"https://daily.dev/agustinbarrientos","image":"https://media.daily.dev/image/upload/s--5ayxQnqn--/f_auto/v1788281802/avatars/avatar_wQYYVe5Tbj0NJ7C7qPoa8?_a=BAMAMicg0"}}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/august-2026-security-vulnerability-what-happened--vf4dqe4hg#faq","mainEntity":[{"@type":"Question","name":"What was the root cause of the Metabase password reset SQL injection vulnerability disclosed in August 2026?","acceptedAnswer":{"@type":"Answer","text":"A chained flaw across four layers: Malli API type annotations did not reject extra keys in the /reset-password request body, an auth refactor from November 11, 2025 began passing the entire body instead of just token and password, the auth flow looked up users by ID via Toucan2's select-one, and HoneySQL treated a 'raw' key in the filter predicate as literal SQL to execute, letting an attacker inject SQL through a crafted user_id parameter. Teams running Metabase can track the disclosed attack chain on daily.dev to confirm they're patched."}},{"@type":"Question","name":"Which Metabase versions were affected by the August 2026 zero-day and when was it patched?","acceptedAnswer":{"@type":"Answer","text":"All Metabase installations running version 0.58 and later were vulnerable. The vulnerability was discovered after a customer reported an anomalous API key creation on August 3, 2026, and patches were packaged and released on August 6, 2026, with a further hardening release, version 63.13, following shortly after. daily.dev helps developers stay on top of urgent patch timelines like this Metabase fix."}},{"@type":"Question","name":"How did attackers exploit the Metabase SQL injection to gain access?","acceptedAnswer":{"@type":"Answer","text":"Attackers submitted a password-reset request with a user_id field containing a raw SQL payload such as {\"raw\": \"1);INSERT INTO ...; --\"}, which HoneySQL executed literally, inserting a forged session record tied to user ID 1, the default admin account. That session was then used to browse data and create an API key enabling bulk table downloads. Understanding real exploit chains like this helps developers harden their own auth flows, something daily.dev readers track closely."}}]}
```

