← Back
CVE-2026-44788
medium
CVSS 5.9
Path Traversal in SharpCompress (CVE-2026-44788)
Summary
path traversal in SharpCompress (CVE-2026-44788). Data can be tampered with by attackers. Exploitable via ``WriteToDirectoryInternal``. Mitigation: upgrade to `0.48.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-44788** has been found in SharpCompress.
Attackers can target a specific entry point like ``WriteToDirectoryInternal`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 5.9/10.
What to do: upgrade SharpCompress to **0.48.0** or later.
If unsure, ask your IT team or search "SharpCompress CVE-2026-44788" on the vendor's site.
CVE-2026-44788 (SharpCompress) — CWE-22 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `WriteToDirectoryInternal` / `WriteToDirectoryAsyncInternal` / `Directory.CreateDirectory` / `Path.Combine`
Patched: `0.48.0` — apply immediately
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 SharpCompress. Attackers reach the vulnerable code path via ``WriteToDirectoryInternal`` without authentication.
📍 Affected scope
SharpCompress — . Attack surface: `WriteToDirectoryInternal` / `WriteToDirectoryAsyncInternal` / `Directory.CreateDirectory` / `Path.Combine`.
🔥 Severity
Severity: Medium (CVSS 5.9/10). Data can be tampered with by attackers
🔧 How to fix
Update to **0.48.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'SharpCompress' .` 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 'SharpCompress' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `SharpCompress` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade SharpCompress to 0.48.0ステージング環境で 0.48.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
nuget
SharpCompress
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.48.0"}]}]
References
- exploit 134c704f-9b21-4f2e-91b3-4a467353bcc0
- package https://github.com/adamhathcock/sharpcompress
- web https://github.com/advisories/GHSA-6c8g-7p36-r338
- web https://nvd.nist.gov/vuln/detail/CVE-2026-44788
- web https://github.com/adamhathcock/sharpcompress/commit/2021a06626d0555a4d69471386e763ca5f5d5dfb