Vulnerability Database · Debian · Package report

php5: vulnerability history, versions and safety

php5 is a package in the Debian ecosystem. Vulert records 28 vulnerabilities for it across 48 releases, from Jun 2014 to May 2018. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
28 vulnerabilities recorded U28
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 09 May 2018. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 28 vulnerabilities on record across 3 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 28 over 3 years · 0 in the last year i
  • Latest disclosure 09 May 2018 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.

i
Version Vulert vulnerabilities Fix published Details
5.4.45-0+deb7u13 U1 Yes Details →
5.4.45-0+deb7u12 U2 Yes Details →
5.4.45-0+deb7u11 U3 Yes Details →
5.4.45-0+deb7u10 U4 Yes Details →
5.4.45-0+deb7u9 U5 Yes Details →
5.4.45-0+deb7u8 U6 Yes Details →
5.4.45-0+deb7u7 U7 Yes Details →
5.4.45-0+deb7u6 U8 Yes Details →
5.4.45-0+deb7u5 U9 Yes Details →
5.4.45-0+deb7u4 U10 Yes Details →
5.4.45-0+deb7u3 U11 Yes Details →
5.4.45-0+deb7u2 U12 Yes Details →
5.4.45-0+deb7u1 U13 Yes Details →
5.4.44-0+deb7u1 U14 Yes Details →
5.4.41-0+deb7u1 U15 Yes Details →
5.4.39-0+deb7u2 U16 Yes Details →
5.4.39-0+deb7u1 U17 Yes Details →
5.4.38-0+deb7u1 U18 Yes Details →
5.4.36-0+deb7u3 U19 Yes Details →
5.4.36-0+deb7u1 U20 Yes Details →
5.4.35-0+deb7u2 U21 Yes Details →
5.4.35-0+deb7u1 U22 Yes Details →
5.4.34-0+deb7u1 U23 Yes Details →
5.4.15-1 U24 Yes Details →
5.4.11-1 U24 Yes Details →
5.4.9-4 U24 Yes Details →
5.4.9-3 U24 Yes Details →
5.4.9-2 U24 Yes Details →
5.4.9-1 U24 Yes Details →
5.4.8-1 U24 Yes Details →
5.4.6-2 U24 Yes Details →
5.4.6-1 U24 Yes Details →
5.4.4-15.1 U24 Yes Details →
5.4.4-15 U24 Yes Details →
5.4.4-14 U28 Yes Details →
5.4.4-14+deb7u14 U24 Yes Details →
5.4.4-14+deb7u13 U24 Yes Details →
5.4.4-14+deb7u12 U25 Yes Details →
5.4.4-14+deb7u11 U26 Yes Details →
5.4.4-14+deb7u10 U27 Yes Details →
5.4.4-14+deb7u9 U28 Yes Details →
5.4.4-14+deb7u8 U28 Yes Details →
5.4.4-14+deb7u7 U28 Yes Details →
5.4.4-14+deb7u5 U28 Yes Details →
5.4.4-14+deb7u4 U28 Yes Details →
5.4.4-14+deb7u3 U28 Yes Details →
5.4.4-14+deb7u2 U28 Yes Details →
5.4.4-14+deb7u1 U28 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2014 8
  • 2015 8
  • 2016 4
  • 2017 5
  • 2018 3

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

03 Vulnerabilities

Recorded vulnerabilities for php5

The 5 most severe of 28 vulnerabilities recorded for this package

Search all 28 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Security Update for php5 N/A unrated 5.4.45-0+deb7u9 21 Jul 2017
Security Update for php5 N/A unrated 5.4.45-0+deb7u2 27 Oct 2015
Security Update for php5 N/A unrated 5.4.44-0+deb7u1 27 Aug 2015
Vulnerability in php5 - security update (DLA-628-1) N/A unrated 5.4.45-0+deb7u5 18 Sep 2016
Vulnerability in php5 - security update (CVE-2015-8865) N/A unrated 5.4.45-0+deb7u3 31 May 2016

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 28 vulnerabilities for php5 in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 28 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?

28 vulnerabilities are recorded for php5 in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 28 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 01 Jun 2014. 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.