Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
CISA KEV·Added 2022-08-25 — agencies required to remediate by 2022-09-15
🐘 Packagist

CVE-2020-28949

HIGH

Multiple vulnerabilities through filename manipulation in Archive_Tar

Also known asBIT-drupal-2020-28948BIT-drupal-2020-28949CVE-2020-28948DRUPAL-CORE-2020-013GHSA-75c5-f4gw-38r9GHSA-jh5x-hfhg-78jq
Published
Nov 19, 2020
Updated
Apr 16, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
6 known

EPSS Exploitation Probability

via FIRST.org ↗
93.4%probability of exploitation in next 30 days
Very High Risk100th percentile0.00%
92.5%92.9%93.4%93.9%93.4%93.4%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

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

Archive_Tar through 1.4.10 has :// filename sanitization only to address phar attacks, and thus any other stream-wrapper attack (such as file:// to overwrite files) can still succeed.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistpear/archive_tarall versions1.4.11
Exploits & PoCs
6

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Frequently Asked Questions

Archive_Tar through 1.4.10 has :// filename sanitization only to address phar attacks, and thus any other stream-wrapper attack (such as file:// to overwrite files) can still succeed.
O3 Security · Impact-Aware SCA

Is CVE-2020-28949 in your stack?

O3 detects CVE-2020-28949 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.