CVE-2026-100406: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in dbt-labs dbt-core
Description
A path traversal vulnerability (CWE-22) exists in dbt-labs dbt-core versions from 2.0.0-alpha.0 up to but not including 2.0.0-alpha.5. The dbt docs serve component exposes an unauthenticated POST /api/v1/query endpoint that allows an attacker with network access to execute arbitrary SQL queries via DuckDB, including filesystem-reading functions. This can lead to unauthorized reading of files accessible to the dbt process outside the intended docs index directory. The server binds to localhost by default but can be exposed to the network by configuration. The issue is fixed in version 2.0.0-alpha.5.
CVSS v4.0
Score 8.2high
Affected software
dbt-labs
dbt-core
pkg:github/dbt-labs/dbt-coreRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
dbt-labs dbt-core versions >=2.0.0-alpha.0 and <2.0.0-alpha.5 contain a path traversal vulnerability in the dbt docs serve component. The unauthenticated POST /api/v1/query endpoint passes user-supplied SQL to DuckDbViewsBackend::query_arrow() without authorization or allowlisting. This allows an attacker who can reach the server to invoke DuckDB filesystem-reading functions, potentially reading arbitrary files accessible to the dbt process, including files outside the intended docs index directory. By default, the server binds to localhost, limiting exposure, but operators can configure it to listen on external interfaces, increasing risk. The vulnerability is addressed in version 2.0.0-alpha.5.
Potential Impact
An attacker with network access to the vulnerable dbt docs serve endpoint can read arbitrary files accessible to the dbt process by exploiting the path traversal vulnerability. This can lead to unauthorized disclosure of sensitive information stored on the filesystem. There is no indication of privilege escalation or remote code execution from the provided data. The default localhost binding reduces exposure, but misconfiguration can expose the service externally, increasing risk.
Mitigation Recommendations
Upgrade dbt-core to version 2.0.0-alpha.5 or later, where this vulnerability is fixed. If upgrading is not immediately possible, ensure that the dbt docs serve endpoint is not exposed to untrusted networks by keeping the server bound to localhost and restricting network access. Monitor configuration settings such as the host option or DBT_DOCS_HOST to prevent unintended exposure. Patch status is confirmed fixed in 2.0.0-alpha.5.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-09-25T20:08:33.084Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6acfceab2cdf04f656a1f70e
Added to database: 10/14/2026, 18:49:15 UTC
Last enriched: 10/14/2026, 19:02:36 UTC
Last updated: 10/14/2026, 19:28:22 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.