Repository navigation
fix(docker): update PHP to 8.3.36 to fix CVE-2026-109618 and CVE-2026-109619 - #217
Conversation
…-109619 wordpress:6.8-php8.3-fpm isn't rebuilt anymore and is stuck on PHP 8.3.28. Same for phpmyadmin/phpmyadmin (8.3.26), so the override example now uses the official phpmyadmin image.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
The php container builds from
wordpress:6.8-php8.3-fpm, and that tag hasn't been rebuilt since WordPress 6.9 came out, so it's stuck on PHP 8.3.28. That version is affected by the two RCEs PHP fixed yesterday (CVE-2026-109618 and CVE-2026-109619, see the advisory), anddocker compose build --pulldoesn't help since the tag itself never moves.Switched to
wordpress:php8.3-fpm, which is on 8.3.36 and keeps getting rebuilt. I left the WordPress version out of the tag on purpose so we don't end up here again with the next WordPress release. WordPress itself lives in thewordpress-srcvolume, so existing installs keep their version and only fresh installs start from the newer one.The phpmyadmin example in
data/docker/docker-compose.override.ymlhad the same problem:phpmyadmin/phpmyadminis still on PHP 8.3.26 and runs Apache mod_php, which the advisory calls the highest risk. It now points to the officialphpmyadminimage, which is on 8.3.36.To pick it up:
docker compose build --pull php && docker compose up -d php, plusdocker compose pull phpmyadminif you use the override.Didn't build it locally, the CI here builds the php image and checks the containers come up. Both new images report PHP 8.3.36 on Docker Hub.
Summary by CodeRabbit