# CVE-2026-100406: dbt: Unauthenticated Arbitrary SQL Execution in `dbt docs serve`

> Unauthenticated SQL injection in dbt docs serve allows attackers to read arbitrary files and execute code if the server is exposed to the network.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-h2j2-2r7g-rff8

## What is CVE-2026-100406?

CVE-2026-100406 is a high-severity SQL injection vulnerability in dbt-labs dbt-core, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

dbt enables data analysts and engineers to transform their data using the same practices that software engineers use to build applications. From 2.0.0-alpha.0 until 2.0.0-alpha.5, dbt docs serve exposes the unauthenticated POST /api/v1/query endpoint in crates/dbt-docs-server/src/handlers/query.rs, which passes caller-supplied SQL to DuckDbViewsBackend::query_arrow() in crates/dbt-index-core/src/backend.rs without authorization or an allowlist. A client that can reach the server can invoke DuckDB filesystem-reading functions to read files available to the dbt process, including files outside the docs index directory. The server binds to localhost by default, but operators can expose it to a network through the host option or DBT_DOCS_HOST setting. This issue is fixed in version 2.0.0-alpha.5.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-100406?


## How do I fix CVE-2026-100406?

No fix has been published for CVE-2026-100406 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-100406 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100406 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-100406 and fix it if it is affected.

What it is: CVE-2026-100406 is a high-severity SQL injection vulnerability in dbt-labs dbt-core, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100406 exists.

Affected product: dbt-labs dbt-core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-100406/ (Markdown: https://insights.sbomify.com/CVE-2026-100406/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-100406
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-100406
- OSV: https://osv.dev/vulnerability/CVE-2026-100406

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-100406/
Summaries are generated and may contain mistakes; the official description above is the record.