Path Traversal in uv (CVE-2026-104843)
Summary
Path traversal in uv (CVE-2026-104843). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.12.18 or later.
Original description
The description as published by the source.
Impact
In versions of uv from 0.12.7 to 0.12.18 on Windows, uv could be induced into writing a file outside of the installation prefix during wheel installation.
A malicious wheel could use this to place an executable outside of the intended environment, including in a directory already present on the user's PATH.
This vulnerability only affects Windows hosts; no other platforms are affected.
Patches
uv 0.12.18 and newer address this vulnerability. Users are encouraged to upgrade to 0.12.18.
Workarounds
There is no workaround other than upgrading to uv 0.12.18.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-104843 has been found in uv.
Risk of unauthorized operations or information disclosure.
What to do: upgrade uv to 0.12.18 or later.
If unsure, ask your IT team or search "uv CVE-2026-104843" on the vendor's site.
CVE-2026-104843 (uv) — CWE-22
Patched: 0.12.18 — apply immediately
Workaround: There is no workaround other than upgrading to uv 0.12.18.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in uv.
Check the vendor advisory for the affected versions of uv.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.12.18.
Workaround: There is no workaround other than upgrading to uv 0.12.18.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'uv' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'uv' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
uvを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
There is no workaround other than upgrading to uv 0.12.18.パッチが適用されるまでの応急処置として、There is no workaround other than upgrading to uv 0.12.18. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade uv to 0.12.18ステージング環境で 0.12.18 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com