Vulnerability in tar (CVE-2026-59875)
Summary
Vulnerability in tar (CVE-2026-59875). Risk of unauthorized operations or information disclosure. Exploitable via NUL. Mitigation: upgrade to 7.5.17 or later.
Original description
The description as published by the source.
node-tar is a tar archive manipulation library for Node.js. Prior to 7.5.17, node-tar does not strip NUL bytes from PAX path and linkpath records in src/pax.ts, allowing a crafted archive with values to reach fs.lstat or fs.open and terminate the process with an uncaught exception. This issue is fixed in version 7.5.17.
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-59875 has been found in tar.
Attackers can target a specific entry point like NUL over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade tar to 7.5.17 or later.
If unsure, ask your IT team or search "tar CVE-2026-59875" on the vendor's site.
CVE-2026-59875 (tar) — CWE-248 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: NUL / entry.path / ERR_INVALID_ARG_VALUE / FSReqCallback
Patched: 7.5.17 — 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.
A vulnerability (CWE-248) exists in tar. Attackers reach the vulnerable code path via NUL without authentication.
Check the vendor advisory for the affected versions of tar. Attack surface: NUL / entry.path / ERR_INVALID_ARG_VALUE / FSReqCallback.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 7.5.17.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'tar' . 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 'tar' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
tarを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade tar to 7.5.17ステージング環境で 7.5.17 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-59875 node-tar
- Ubuntu UBUNTU-CVE-2026-59875 node-tar
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- patch github.com
- web github.com
- web github.com