The images take PHP from Ondřej Surý's packages. When a security release of PHP is announced:
- An issue is opened on this repository: subscribe to it to be notified, ask your questions there. Its description gives the state of each image, checked every 5 minutes, and a comment is posted when it changes, every 30 minutes at most.
- Each PHP version is rebuilt as soon as its fixed packages are published on amd64 or arm64, and rebuilt again when the other arch follows: sury publishes the arm64 packages later, sometimes a day later.
Outside of the security releases, each PHP version is also rebuilt within a day when sury publishes new packages.
The tags of the images:
X.Y-v5-*(e.g.8.4-v5-apache) is updated at each build: use it to get the fixes.X.Y.Z-v5-*(e.g.8.4.28-v5-apache) is the last build of PHP X.Y.Z: it is published once amd64 and arm64 have the same PHP version, then updated by each build until the next PHP version. Use the digest of an image to pin it.- PHP 7.4, 8.0 and 8.1 are not maintained: they are rebuilt when sury publishes a fix for them, which keeps the PHP
version number, without new
X.Y.Ztag.
php-watch.yml checks the packages of sury every day, and launches
workflow.yml and legacy-v5.yml for each PHP version whose images do not have them. The schedules of GitHub can
start hours late: for a security release, launch it by hand the day before, it checks every 5 minutes from start_at:
$ gh variable set SECURITY_RELEASE --body 1
$ gh workflow run php-watch.yml --ref v5 -f issue=437 -f start_at="2026-12-17 13:45" -f until="2026-12-19 14:00" \
-f fixed="8.5=8.5.14 8.4=8.4.29 8.3=8.3.38 8.2=8.2.37"fixedgives the fixed versions once they are known (the watch can be launched again with them): the table says fixed or vulnerable instead of up to date. Withoutfixed, the watch stops as soon as the images have the packages of sury.SECURITY_RELEASE=1pauses the builds of the pushes, of the pull requests and the weekly build with its purge of the cache: only the rebuilds of the watch publish images. The labelforce-ciruns the CI of a pull request anyway.- Afterwards:
gh variable set SECURITY_RELEASE --body 0, thengh workflow run workflow.yml --ref v5to publish the commits merged meanwhile.
-
Pull the images again and recreate your containers:
$ docker compose pull && docker compose up -d -
Rebuild the images built from ours, without the cache of the base image:
$ docker build --pull -t my-app .In your CI, check that the base image is pulled again and not taken from a cache.
-
Check the PHP version of your containers (
php -v) against the fixed versions given in the issue.
Watchtower pulls the new versions of the images and recreates the containers, so that the next security fixes are applied without waiting for you:
$ docker run -d --name watchtower -v /var/run/docker.sock:/var/run/docker.sock \
ghcr.io/nicholas-fedor/watchtowerThe v4 images get no security fix: migrate to v5, see the migration notes.
- 2026-11-19: 17 vulnerabilities, 7 of them critical
(CVE-2026-115560, CVE-2026-126714, CVE-2026-129481, CVE-2026-129496, CVE-2026-129289, CVE-2026-129474,
CVE-2026-129182), fixed in PHP 8.2.36, 8.3.37, 8.4.28 and 8.5.13. PHP 7.4, 8.0 and 8.1 got the sury backport of the
12 vulnerabilities fixed in 8.2.36 (
1:7.4.33-36,1:8.0.30-30,8.1.34-13). All the v5 images were fixed on amd64 on 2026-11-19 and on arm64 on 2026-11-20. See issue #437. - 2026-10-21: php2shell (CVE-2026-109618 and CVE-2026-109619), fixed in all the v5 images.