CVE-2026-100406 dbt-labs CVE debrief

Who should care

Operators and administrators of dbt-core, especially those who expose the `dbt docs serve` command to a network, should assess exposure and prioritize remediation. This includes reviewing current version usage, verifying potential exposure, and applying fixes or mitigations as needed. Security teams and vulnerability management teams should also be aware of this issue and coordinate with operators and administrators to ensure timely remediation.

Why it matters

CVE-2026-100406 is a high-severity vulnerability in dbt-core that allows unauthenticated arbitrary SQL execution, potentially leading to unauthorized file reads and exploitation by attackers.

• Potential unauthorized file reads
• Possible exploitation by attackers to read sensitive files
• Need for verification of current version and exposure
• Prioritization of remediation efforts

Technical summary

The vulnerability exists in the `dbt docs serve` command, which exposes the unauthenticated POST /api/v1/query endpoint. This endpoint passes caller-supplied SQL to DuckDbViewsBackend::query_arrow() without authorization or an allowlist. An attacker can invoke DuckDB filesystem-reading functions to read files available to the dbt process, potentially leading to unauthorized file reads. The server binds to localhost by default, but operators can expose it to a network through the host option or DBT_DOCS_HOST setting.

Defensive priority

Operators and administrators of dbt-core should assess exposure and prioritize remediation, especially if the `dbt docs serve` command is exposed to a network.

Recommended defensive actions

• Assess exposure of `dbt docs serve` to a network
• Verify if the current version of dbt-core is vulnerable
• Apply the fix by upgrading to version 2.0.0-alpha.5 or later
• Monitor for potential exploitation attempts
• Review compensating controls for exposed systems
• Check relevant monitoring, detection, and logs for exposed assets
• Track exceptions and retest remediated assets

Evidence notes

The vulnerability is confirmed by the CVE Program and NVD. The dbt-labs vendor has provided an advisory and a fix for the issue. Evidence is limited to public CVE details and vendor advisories. Defenders should verify current version exposure and apply the fix. Additional verification tasks may be needed based on specific environment configurations and potential exposure to the `dbt docs serve` command.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.