Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.8Exploited · CISA KEV

Multiple vulnerabilities through filename manipulation in Archive_Tar

CVE-2020-28949GHSA-75c5-f4gw-38r9

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (pear/archive_tar 1.4.11), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
Confirmed: listed in the CISA Known Exploited Vulnerabilities catalog.
CVSS
7.8 · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:H
EPSS
  • CVE-2020-28949: 84.55% estimated exploitation activity in the next 30 days; percentile 99.70 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

ArchiveTar 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. See: https://github.com/pear/ArchiveTar/issues/33

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-75c5-f4gw-38r9

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-28949

Advisory: Multiple vulnerabilities through filename manipulation in Archive_Tar
IDs: CVE-2020-28949, GHSA-75c5-f4gw-38r9
Record: https://patchnext.com/advisories/cve-2020-28949 (revision 1, source checked 26 Oct 2026, 14:34 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.8)
Exploitation: confirmed: listed in the CISA Known Exploited Vulnerabilities catalog.
Vendor response: Vendor fix available; fixed versions by package: pear/archive_tar 1.4.11. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist pear/archive_tar: affected < 1.4.11; fixed in 1.4.11

## Suggested inspection (read-only)
- Packagist pear/archive_tar: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pear/archive_tar.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-75c5-f4gw-38r9 (GitHub-reviewed advisory GHSA-75c5-f4gw-38r9 lists affected ranges: Packagist pear/archive_tar >=0 <1.4.11)
- Verified: https://www.cisa.gov/known-exploited-vulnerabilities-catalog (CISA added CVE-2020-28949 to the Known Exploited Vulnerabilities catalog on 2022-08-25.)

Commands are suggestions: review each one before running it.

Loading voting…