VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

php-pear: vulnerability history, versions and safety

php-pear is a package in the Debian ecosystem. Vulert records 11 vulnerabilities for it across 7 releases, from Feb 2017 to Jul 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
11 vulnerabilities recorded U11
i
3 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all php-pear vulnerabilities

Vulert verdict on php-pear i

Updated on 23 Oct 2026

Careful: 3 of the 11 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 11 vulnerabilities on record across 4 years, none in the last year.

What to do: Plan around the 3 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 11 over 4 years · 0 in the last year i
  • Latest disclosure 30 Jul 2021 i
  • Highest CVSS 8.8 i
  • With no published fix 3 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for php-pear, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 7 of 7 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 2
  • 2018 2
  • 2020 4
  • 2021 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 11 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for php-pear

The 5 most severe of 11 vulnerabilities recorded for this package

Search all 11 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Object Injection Vulnerability in PEAR Archive_Tar Package 8.8 high 1:1.10.6+submodules+notgz-1.1 28 Dec 2018
Critical File Overwrite Vulnerability in php-pear: Archive_Tar Package 7.8 high 1:1.10.9+submodules+notgz-1.1 19 Nov 2020
Unserialization Vulnerability in Archive_Tar Affecting PHP Pear Package 7.8 high 1:1.10.9+submodules+notgz-1.1 19 Nov 2020
File Overwrite Vulnerability in PEAR Base System v1.10.1 7.5 high No fix published 01 Feb 2017
Directory Traversal Vulnerability in php-pear Package - CVE-2020-36193 7.5 high 1:1.10.12+submodules+notgz+20210212-1 18 Jan 2021

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About php-pear

Is php-pear safe to use?

Vulert records 11 vulnerabilities for php-pear in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 11 not yet rated. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does php-pear have?

11 vulnerabilities are recorded for php-pear in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 11 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new php-pear vulnerabilities disclosed?

0 vulnerabilities were recorded for php-pear in the last 12 months, and the oldest entry in this database dates to 01 Feb 2017. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of php-pear are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor php-pear for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the php-pear version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.