← Back
GHSA-4gg8-gxpx-9rph
Path Traversal in uv (GHSA-4gg8-gxpx-9rph)
Summary
path traversal in uv (GHSA-4gg8-gxpx-9rph). Risk of unauthorized operations or information disclosure. Exploitable via ``console_scripts``. Mitigation: upgrade to `0.11.15` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-4gg8-gxpx-9rph** has been found in uv.
Attackers can target a specific entry point like ``console_scripts`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade uv to **0.11.15** or later.
If unsure, ask your IT team or search "uv GHSA-4gg8-gxpx-9rph" on the vendor's site.
GHSA-4gg8-gxpx-9rph (uv) — CWE-22 /
Attack surface: `console_scripts` / `gui_scripts` / `PATH`
Patched: `0.11.15` — apply immediately
Workaround: There is no workaround other than upgrading to uv 0.11.15.
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.
❓ What is the problem
**Path traversal** (CWE-22) exists in uv. Attackers reach the vulnerable code path via ``console_scripts`` without authentication.
📍 Affected scope
uv — . Attack surface: `console_scripts` / `gui_scripts` / `PATH`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.11.15**.
🛡️ Workaround
Workaround: There is no workaround other than upgrading to uv 0.11.15.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
There is no workaround other than upgrading to uv 0.11.15.パッチが適用されるまでの応急処置として、There is no workaround other than upgrading to uv 0.11.15. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade uv to 0.11.15ステージング環境で 0.11.15 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
uv
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.11.15"}]}]
rust
uv
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.11.15"}]}]
PyPI
uv
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.11.15"}]}]
crates.io
uv
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.11.15"}]}]