Skip to main content

Security-Patched PHP for CentOS 6

CentOS 6 went EOL in November 2020. Everpatch keeps its PHP patched: the stock PHP 5.3 and Remi-compatible PHP 7.0 and 7.1, as signed RPMs that update in place.

No per-server contracts, no agents, no lock-in — packages from the same GetPageSpeed repository, with the same package names you already run.

The EL6 gap

CentOS 6 reached end of life on November 30, 2020, and its stock PHP 5.3.3 stopped receiving fixes with it. PHP 7.0 and 7.1 had already ended upstream. Every PHP security release since then has skipped CentOS 6, while servers that cannot be rebuilt yet keep serving traffic on it.

Everpatch PHP ports the current php-src security fixes to these branches and builds them for EL6, so the known holes get closed while your migration happens on its own timeline.

PHP channels for CentOS 6

PHP 5.3

109 CVE fixes tracked in this channel's security notes.

Everpatch PHP 5.3 for CentOS 6 →

PHP 7.0

82 CVE fixes tracked in this channel's security notes.

Everpatch PHP 7.0 for CentOS 6 →

PHP 7.1

61 CVE fixes tracked in this channel's security notes.

Everpatch PHP 7.1 for CentOS 6 →

Start here

yum -y install https://extras.getpagespeed.com/release-latest.rpm

One release RPM wires up the repository and GPG key. Each PHP channel above has its one-command update on its page.

Honest scope

On CentOS 6, Everpatch covers PHP only. The kernel, OpenSSL, glibc and the rest of the base OS stay as CentOS 6 left them. PHP 7.0 and 7.1 ship base-name php-* packages only, with no software collection builds; your existing el6 PECL extensions keep loading. Need contractual coverage with an SLA and invoice/PO procurement? Enterprise agreements add exactly that on top of the same packages.

Frequently asked questions

Which PHP versions are covered on CentOS 6?

PHP 5.3, the stock CentOS 6 PHP, as a drop-in update for the php-5.3.3 packages, plus PHP 7.0 and 7.1 as in-place updates for Remi's el6 remi-php70 and remi-php71 packages. All three are x86_64 RPMs signed by GetPageSpeed.

Do I need EPEL or other repositories?

No. The libraries the builds need beyond CentOS 6 itself come from the GetPageSpeed repository, so a fresh CentOS 6 host needs only the release package.

Does Everpatch cover the CentOS 6 kernel or base OS?

No. On CentOS 6 Everpatch covers the PHP layer only. The maintained kernel and base OS packages are a CentOS 7 offering.

Do I need a subscription?

Not for personal, development or evaluation use: the PHP packages install from the public GetPageSpeed repository with no signup. Commercial production use requires a subscription under the repository terms: GetPageSpeed Ultra ($500/year) for up to 10 servers running your own services, or GetPageSpeed Fleet (from $800/year) for servers that host client websites or fleets larger than 10. Either one funds these backports and keeps your servers covered for the next EOL PHP CVE. Organizations with 250+ employees or $10M+ revenue, or anyone needing a contractual SLA and invoice/PO procurement, should contact us about Enterprise. To license servers without registering IP addresses, place your license file at /etc/getpagespeed/license.jwt.