# dbt-common's commonprefix() doesn't protect against path traversal

Advisory record · `GHSA-w75w-9qv4-j5xj`

- **Identifiers:** `GHSA-w75w-9qv4-j5xj` · `CVE-2026-29790` · `PYSEC-2026-2440`
- **State:** Confirmed
- **Severity:** CVSS 2.0 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 5 Mar 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 5 Mar 2026, 00:59 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `dbt-common` (PyPI): affected `<1.34.2 || >=1.35.0, <1.37.3`; fixed in `1.34.2`, `1.37.3`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> dbt-common versions before 1.34.2 and from 1.35.0 before 1.37.3 are affected by a path traversal flaw in its safe_extract() tarball extraction function, which uses a character-based prefix check that can let files land in sibling directories with matching name prefixes. An attacker would need a malicious tarball that the user processes, such as a package installed from an untrusted source, and could then write files outside the intended directory. Upgrade to dbt-common 1.34.2 or 1.37.3; the source lists no workaround beyond only installing packages from trusted sources.

Written 5 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 2.0 Low, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0031, the 23rd percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:34 UTC: First seen by agentprime
- 31 Oct 2026, 14:34 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-w75w-9qv4-j5xj)

## Sources

- [GitHub Advisory Database: GHSA-w75w-9qv4-j5xj](https://github.com/advisories/GHSA-w75w-9qv4-j5xj)
- [OSV: GHSA-w75w-9qv4-j5xj](https://osv.dev/vulnerability/GHSA-w75w-9qv4-j5xj)
- <https://github.com/dbt-labs/dbt-common/security/advisories/GHSA-w75w-9qv4-j5xj>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-29790>
- <https://github.com/pypa/pip/pull/13777>
- <https://github.com/dbt-labs/dbt-common/commit/e547954a48bac9394ef6eb98432e429dce9a7709>
- <https://docs.python.org/3/library/os.path.html#os.path.commonpath>
- <https://github.com/advisories/GHSA-6vgw-5pg2-w6jp>
- <https://github.com/dbt-labs/dbt-common>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-w75w-9qv4-j5xj>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-w75w-9qv4-j5xj/>. Everything for agents: <https://agentprime.io/llms.txt>.
