Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
HIGH severity

Directory Traversal in Archive_TarGHSA-p8q8-jfcv-g2h2

HIGHFix: pear/Archive_Tar@7789ebb

GHSA-p8q8-jfcv-g2h2 is a high-severity (CVSS 7.1) CWE-59 vulnerability in pear/archive_tar. EPSS puts its 30-day exploitation probability at 73.4% (99th percentile). A fix is available for pear/archive_tar — see the affected versions and patch details below.

Also known asCVE-2021-32610DRUPAL-CORE-2021-004
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
73.4%probability of exploitation in next 30 days
Very High Risk0.00%
Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk
0.00%31.5%63.0%94.5%2.9%73.4%Apr 26Aug 26Oct 26

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

How urgent is this, really

GHSA-p8q8-jfcv-g2h2 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected
🐘pear/archive_tar

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

Description

In Archive_Tar before 1.4.14, symlinks can refer to targets outside of the extracted archive, a different vulnerability than CVE-2020-36193.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistpear/archive_tarall versions1.4.14composer require pear/archive_tar:^1.4.14

Affected Products

3 products · 5 configurations
OS
debian linuxdebian
1 version
9.0
OS
fedorafedoraproject
3 versions
333435
Application
archive tarphp
< 1.4.14
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 pear/archive_tar, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update pear/archive_tar to 1.4.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p8q8-jfcv-g2h2 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
ProductFixed inAdvisory
Red Hat Enterprise Linux 8php:7.4-8070020220707122009.afd00e68RHSA-2022:7628

Frequently Asked Questions

In Archive_Tar before 1.4.14, symlinks can refer to targets outside of the extracted archive, a different vulnerability than CVE-2020-36193.
O3 Security · Impact-Aware SCA

Is GHSA-p8q8-jfcv-g2h2 in your dependencies?

Find it across Packagist, including transitive dependencies.

Directory Traversal in Archive_Tar (High 7.1)