How severe is GHSA-w75w-9qv4-j5xj?

No CVSS score has been assigned to GHSA-w75w-9qv4-j5xj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w75w-9qv4-j5xj?

GHSA-w75w-9qv4-j5xj affects the following packages: dbt-common (PyPI), dbt-common (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-w75w-9qv4-j5xj?

Update dbt-common to 1.34.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w75w-9qv4-j5xj is resolved across your whole dependency graph.

How do I detect GHSA-w75w-9qv4-j5xj in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dbt-common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-w75w-9qv4-j5xj if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-w75w-9qv4-j5xj?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-w75w-9qv4-j5xj can be triaged on real exposure rather than presence alone.

Is GHSA-w75w-9qv4-j5xj actively exploited in the wild?

No public exploit code has been indexed for GHSA-w75w-9qv4-j5xj yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-w75w-9qv4-j5xj?

GHSA-w75w-9qv4-j5xj has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 18th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-w75w-9qv4-j5xj?

GHSA-w75w-9qv4-j5xj is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-w75w-9qv4-j5xj published, and has it been updated?

GHSA-w75w-9qv4-j5xj was published on March 5, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

GHSA-w75w-9qv4-j5xj — dbt-common

Fix: pypa/pip#13777

GHSA-w75w-9qv4-j5xj is a Path Traversal vulnerability in dbt-common. A fix is available for dbt-common — see the affected versions and patch details below.

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

Also known asCVE-2026-29790PYSEC-2026-2440

Published

Mar 5, 2026

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Sep 20, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-w75w-9qv4-j5xj.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs18th percentile — riskier than 18% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

2 pkgs affected

🐍dbt-common🐍dbt-common

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

What kind of vulnerability is it? Who is impacted?

A path traversal vulnerability exists in dbt-common's safe_extract() function used when extracting tarball archives. The function uses os.path.commonprefix() to validate that extracted files remain within the intended destination directory. However, commonprefix() compares paths character-by-character rather than by path components, allowing a malicious tarball to write files to sibling directories with matching name prefixes.

For example, when extracting to /tmp/packages, a crafted tarball could write files to /tmp/packagesevil/ by exploiting the character-based prefix matching.

This vulnerability affects users who:

Install dbt packages from untrusted sources
Process tarball archives through dbt-common's extraction utilities

The practical risk is limited because:

Exploitation requires a malicious tarball to be processed
File writes are restricted to sibling directories with matching prefixes (not arbitrary paths)
Packages from trusted sources (dbt Hub) are not affected

This is similar to CVE-2026-1703 in pip, which had a CVSS score of 3.9 (Low).

Patches

Has the problem been patched? What versions should users upgrade to?

Fixed in dbt-common version 1.37.3 & 1.34.2, and patched for dbt-core 1.11.7 and 1.10.20 releases.

The fix replaces os.path.commonprefix() with os.path.commonpath(), which correctly compares paths by their components rather than characters.

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

Only install dbt packages from trusted sources (official dbt Hub, verified git repositories)
Avoid installing packages from untrusted URLs or unverified third parties
Review package contents before installation when sourcing from external locations

Resources

Are there any links users can visit to find out more?

CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'): https://cwe.mitre.org/data/definitions/22.html
CVE-2026-1703 (similar vulnerability in pip): https://nvd.nist.gov/vuln/detail/CVE-2026-1703
pip fix PR #13777: https://github.com/pypa/pip/pull/13777
Python documentation on commonpath vs commonprefix: https://docs.python.org/3/library/os.path.html#os.path.commonpath

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`dbt-common`	all versions	1.34.2`pip install --upgrade 'dbt-common==1.34.2'`
🐍PyPI	`dbt-common`	≥ 1.35.0&&< 1.37.3	1.37.3`pip install --upgrade 'dbt-common==1.37.3'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dbt-common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update dbt-common to 1.34.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w75w-9qv4-j5xj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-w75w-9qv4-j5xj can be triaged on real exposure rather than presence alone.

Tailored to GHSA-w75w-9qv4-j5xj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact _What kind of vulnerability is it? Who is impacted?_ A path traversal vulnerability exists in dbt-common's `safe_extract()` function used when extracting tarball archives. The function uses `os.path.commonprefix()` to validate that extracted files remain within the intended destination directory. However, `commonprefix()` compares paths character-by-character rather than by path components, allowing a malicious tarball to write files to sibling directories with matching name prefixes. For example, when extracting to `/tmp/packages`, a crafted tarball could write files to `/tmp/pac

O3 Security · Impact-Aware SCA

Is GHSA-w75w-9qv4-j5xj in your dependencies?

O3 Security finds GHSA-w75w-9qv4-j5xj across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works

GHSA-w75w-9qv4-j5xj — dbt-common

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

Real-World Exposure

Description

Impact

Patches

Workarounds

Resources

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-w75w-9qv4-j5xj in your dependencies?