Vulnerability Database · Debian · Package report

php5: vulnerability history, versions and safety

php5 is a package in the Debian ecosystem. Vulert records 21 vulnerabilities for it across 25 releases, from Jan 2012 to Feb 2016. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
21 vulnerabilities recorded U21
i
0 with no fix published

Every vulnerability has a patched version to move to.

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.

Vulert verdict on php5 i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 29 Feb 2016. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 21 vulnerabilities on record across 4 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 21 over 4 years · 0 in the last year i
  • Latest disclosure 29 Feb 2016 i
  • Highest CVSS n/a i
  • With no published fix 0 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 php5, 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 25 of 25 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2012 6
  • 2013 4
  • 2014 5
  • 2015 5
  • 2016 1

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

03 Vulnerabilities

Recorded vulnerabilities for php5

The 5 most severe of 21 vulnerabilities recorded for this package

Search all 21 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Buffer Overflow and Inconsistent Parsing in PHP5 N/A unrated 5.3.3-7+squeeze14 13 Aug 2012
Security Update for php5 N/A unrated 5.3.3-7+squeeze23 25 Nov 2014
Vulnerability in php5 package - Denial of Service N/A unrated 5.3.3-7+squeeze24 31 Jan 2015
Vulnerability in php5 package - Regression Update N/A unrated 5.3.3-7+squeeze25 02 Feb 2015
Vulnerability in php5 package - security update N/A unrated 5.3.3.1-7+squeeze26 29 Apr 2015

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 php5

Is php5 safe to use?

Vulert records 21 vulnerabilities for php5 in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 21 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does php5 have?

21 vulnerabilities are recorded for php5 in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 21 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 php5 vulnerabilities disclosed?

0 vulnerabilities were recorded for php5 in the last 12 months, and the oldest entry in this database dates to 31 Jan 2012. 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 php5 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 php5 for upcoming vulnerabilities?

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