Skip to main content

PHP 5.3 Security Patches for CentOS 6

Everpatch PHP keeps the PHP 5.3 that CentOS 6 shipped by default security-patched — a drop-in update for the stock php-5.3.3 packages.

Signed RPM builds of the stock CentOS 6 PHP 5.3.3 with current security fixes hand-ported to the 5.3 codebase. Same package names, same extension ABI and the same /etc/php.d layout, so yum update replaces them in place.

PHP2Shell fixed from 5.3.3-51.el6. How to apply it · Check your server · Scan it with CVEfox

Ultra, $500/year Fleet, from $800/year

The gap

PHP 5.3 was the default PHP of CentOS 6. Upstream PHP 5.3 ended in 2014 and CentOS 6 went end of life in November 2020, so the stock php-5.3.3 packages stopped receiving fixes, while years of PHP security releases kept landing on newer branches only.

Everpatch PHP 5.3 keeps every stock CentOS 6 patch and adds the fixes CentOS 6 never received, from the 2015-2021 backlog to the current PHP security releases, PHP2Shell included: each one ported to the 5.3 engine and audited against upstream and this project's 5.4 ports.

Install

Upgrading stock CentOS 6 PHP 5.3 in place (php-*)

yum -y install https://extras.getpagespeed.com/release-latest.rpm
yum update 'php*'
service httpd restart   # or: service php-fpm restart
php -v

The packages carry the stock CentOS 6 names (php, php-cli, php-common, php-mysql, ...) with higher release numbers and live in the base GetPageSpeed repository, so no channel needs enabling: yum update replaces the stock php-5.3.3 in place and keeps your php.ini and /etc/php.d edits. Hosts already on a PHP 5.4 or newer build are never offered them.

Extensions built for stock CentOS 6 PHP keep loading: the PHP API, Zend extension ABI and configure flags are unchanged. Afterwards php -v prints Built by GetPageSpeed LLC.

Free for personal use. Running it for a business?

Patching EOL PHP is ongoing work: every new PHP CVE has to be ported to branches upstream abandoned years ago, then built and tested on EL6. Commercial production use requires GetPageSpeed Ultra or GetPageSpeed Fleet: either one funds that work and keeps your production servers covered for the next one, together with the full GetPageSpeed repository. When a new fix is ready for the PHP your servers run, we email you the exact command. Ultra covers up to 10 servers running your own services; Fleet is the plan for servers that host client websites, or for more than 10 servers. 250+ employees or $10M+ revenue, or need a contractual SLA and invoice/PO? That is Enterprise.

Ultra, $500/year Fleet, from $800/year Contact us about Enterprise

Security fixes in this channel

The channel's security notes track 109 CVE fixes and 8 further GitHub security advisories that never reached the last vendor build for Enterprise Linux 6.

Fixed in Everpatch PHP 5.3 for CentOS 6
CVE-2010-2950, CVE-2015-5589, CVE-2015-7803, CVE-2015-7804, CVE-2015-8865, CVE-2015-8866, CVE-2015-8874, CVE-2016-2554, CVE-2016-3074, CVE-2016-4070, CVE-2016-4072, CVE-2016-4073, CVE-2016-4342, CVE-2016-4343, CVE-2016-4537, CVE-2016-4538, CVE-2016-4539, CVE-2016-4540, CVE-2016-4541, CVE-2016-4542, CVE-2016-4543, CVE-2016-4544, CVE-2016-5093, CVE-2016-5094, CVE-2016-5096, CVE-2016-5114, CVE-2016-5399, CVE-2016-5766, CVE-2016-5767, CVE-2016-5769, CVE-2016-5771, CVE-2016-5772, CVE-2016-5773, CVE-2016-6289, CVE-2016-6290, CVE-2016-6291, CVE-2016-6292, CVE-2016-6294, CVE-2016-6296, CVE-2016-6297, CVE-2016-7128, CVE-2016-7414, CVE-2016-10158, CVE-2016-10159, CVE-2016-10160, CVE-2016-10167, CVE-2016-10168, CVE-2017-7890, CVE-2017-11147, CVE-2018-5711, CVE-2018-7584, CVE-2018-14851, CVE-2018-17082, CVE-2018-19518, CVE-2018-19935, CVE-2019-9020, CVE-2019-9024, CVE-2019-9637, CVE-2019-9638, CVE-2019-9640, CVE-2019-11034, CVE-2019-11035, CVE-2019-11036, CVE-2019-11040, CVE-2019-11041, CVE-2019-11042, CVE-2019-11045, CVE-2019-11046, CVE-2019-11047, CVE-2019-11048, CVE-2019-11050, CVE-2020-7059, CVE-2020-7063, CVE-2020-7064, CVE-2020-7066, CVE-2020-7067, CVE-2020-7068, CVE-2020-7070, CVE-2020-7071, CVE-2021-21702, CVE-2021-21703, CVE-2021-21705, CVE-2021-21707, CVE-2022-31625, CVE-2022-31628, CVE-2022-31629, CVE-2022-31631, CVE-2023-0567, CVE-2023-0568, CVE-2023-0662, CVE-2023-3247, CVE-2023-3823, CVE-2023-3824, CVE-2024-2756, CVE-2024-5458, CVE-2024-8925, CVE-2024-8927, CVE-2024-11233, CVE-2024-11234, CVE-2025-14181, CVE-2026-6103, CVE-2026-6735, CVE-2026-7261, CVE-2026-7262, CVE-2026-91765, CVE-2026-91766, CVE-2026-92842, CVE-2026-109618, CVE-2026-109619
GHSA-6wmf-4rv5-p3rp, GHSA-88hq-2827-7pg6, GHSA-ch8v-r6jh-4vvr, GHSA-cj93-vc83-wgqv, GHSA-fpwc-w8rq-cr92, GHSA-j3wh-g957-2m85, GHSA-rgrp-mwpx-f6rm, GHSA-w8hw-w9fx-j79w

Fixes are ports of the upstream php-src security patches, audited hunk by hunk; the provenance of every patch is documented per release.

Frequently asked questions

Is PHP 5.3 on CentOS 6 patched for PHP2Shell?

Yes. Everpatch PHP 5.3 carries the backported PHP2Shell fix from 5.3.3-51.el6 onward. The PHP version number does not change, so check the package release rather than php -v, or paste your package list into the PHP2Shell checker. The full walkthrough is in our PHP2Shell guide.

Does it work with the stock CentOS 6 PHP packages?

Yes, that is what it is built for. It ships the same package names as stock CentOS 6 PHP (php, php-cli, php-common, php-mysql, php-gd, ...) with the same configure flags, extension ABI and configuration paths. After installing the release package, yum update 'php*' replaces php-5.3.3 with the patched build; your php.ini and php.d edits are kept.

Is PHP 5.3 still safe to run on CentOS 6?

Safer with this channel than without it: the publicly known PHP vulnerabilities that apply to 5.3 are being patched here, years after upstream and CentOS stopped. PHP 5.3 remains an end-of-life runtime on an end-of-life OS — plan your upgrade on your own schedule. Everpatch exists so a CVE disclosure does not set that schedule for you.

What if I would rather move to a newer PHP?

On CentOS 6, the PHP 7.0 and PHP 7.1 channels are security-patched the same way. For a 5.3-era codebase that is usually a porting project — until it happens, this channel keeps the known holes closed.

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.