NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
CRITICAL severity

tar-utils Path Traversal vulnerabilityGHSA-jpf8-h7h7-3ppm

CRITICALFix: whyrusleeping/tar-utils@20a6137

GHSA-jpf8-h7h7-3ppm is a critical-severity (CVSS 9.1) Path Traversal vulnerability in github.com/whyrusleeping/tar-utils. A fix is available for github.com/whyrusleeping/tar-utils — see the affected versions and patch details below.

Also known asCVE-2020-36566GO-2021-0106
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • 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-jpf8-h7h7-3ppm.

EPSS Exploitation Probability

via FIRST.org ↗
1.1%probability of exploitation in next 30 days
Lower Risk+0.09%
Lower risk than most CVEs66th percentile — riskier than 66% of all scored CVEsHighest risk
0.12%0.62%1.11%1.61%0.6%1.0%1.0%1.0%1.1%Jun 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐹github.com/whyrusleeping/tar-utils

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

Description

Due to improper path sanitization, archives containing relative file paths can cause files to be written (or overwritten) outside of the target directory.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/whyrusleeping/tar-utilsall versions0.0.0-20201201191210-20a61371de5bgo get github.com/whyrusleeping/tar-utils@v0.0.0-20201201191210-20a61371de5b

Affected Products

1 product · 1 configurations
Application
tar-utilstar-utils_project
< 0.0.0-20201201191210-20a61371de5b
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update github.com/whyrusleeping/tar-utils to 0.0.0-20201201191210-20a61371de5b or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jpf8-h7h7-3ppm is resolved across your whole dependency graph.

  3. Workarounds

    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

Due to improper path sanitization, archives containing relative file paths can cause files to be written (or overwritten) outside of the target directory.
O3 Security · Impact-Aware SCA

Is GHSA-jpf8-h7h7-3ppm in your dependencies?

Find it across Go, including transitive dependencies.

tar-utils Path Traversal vulnerability (Critical 9.1)