Security
This release moves every WordPress and PHP site on PHP 8.2, 8.3, 8.4 and 8.5 to rebuilt easyengine/php8.x images based on PHP's security releases of 2026-11-19: 8.2.36, 8.3.37, 8.4.28 and 8.5.13. Together they fix 17 vulnerabilities, 7 of them rated critical by PHP. Update as soon as you can:
ee cli updateIf you're on a release older than v4.14.1, this takes you straight to v4.14.2 and includes everything in v4.14.1 (nginx 1.31.9 in the proxy) and v4.14.0; read the v4.14.0 upgrade notes first.
Fixed vulnerabilities
Critical:
- CVE-2026-129289: PHP-FPM request smuggling through an unread HTTP request body
- CVE-2026-115560: session serializer mismatch can lead to remote code execution
- CVE-2026-129496: timezone cache use-after-free can lead to remote code execution
- CVE-2026-126714: partially overwritten session files can lead to remote code execution
- CVE-2026-129481: use-after-free after interrupted session shutdown (PHP 8.3 and later)
- CVE-2026-129474: use-after-free in magic method backtraces can lead to remote code execution (PHP 8.5)
- CVE-2026-129182: use-after-free via repopulation of the last fatal error backtrace after shutdown (PHP 8.5)
High:
- CVE-2026-129291: PHP-FPM epoll use-after-free can lead to local privilege escalation
- CVE-2026-128090: PHAR OpenSSL signature bypass via algorithm downgrade
- CVE-2026-128064: mixed-case HTTPS and FTPS URLs can expose data in plaintext
- CVE-2026-127960: denial of service through folded HTTP response headers
Medium:
- CVE-2026-129506: SOAP use-after-free when processing DTD entity references
- CVE-2026-15353: SOAP information disclosure through malformed array dimensions
- CVE-2026-129501: double free during DOM XML serialization
- CVE-2026-129292: PHP-FPM status endpoint XSS via unescaped user and script fields
- CVE-2026-129438: incorrect RFC 3986 URI serialization for oversized input (PHP 8.5)
- CVE-2026-129538: PHP-CGI out-of-bounds read and write during PATH_INFO correction (php-cgi only; EasyEngine sites use PHP-FPM)
Not every vulnerability affects every PHP branch; see each advisory and the PHP 8 ChangeLog.
Several of the critical issues need a non-default setup. Two of them depend on settings EasyEngine turns off by default, so sites that changed them were more exposed until this update:
- CVE-2026-115560 goes through session upload progress. EasyEngine has set
session.upload_progress.enabled = Offfor every site since v4.13.3. Sites that turned it back on in theircustom.iniwere exposed. - CVE-2026-129289 needs persistent FastCGI connections. EasyEngine's nginx configuration doesn't enable them. Sites that added
fastcgi_keep_conn onto a custom nginx configuration were exposed.
Upgrade notes
WordPress and PHP sites on PHP 8.2 to 8.5 are recreated
ee cli update is the only step: it moves your existing sites to the patched images. During the update, each enabled site on PHP 8.2, 8.3, 8.4 or 8.5 is recreated on its new image, one site at a time. A temporary support container keeps serving each site while its new image is downloaded and its containers are switched. Requests can stall or fail for a few seconds when traffic moves to the support container and again when it moves back (in our tests, under 5 seconds per switch on a test server and under half a second on a GitHub runner). The first site of each PHP version waits while that image is downloaded (a few hundred MB to download, about 1.5 GB on disk). HTML sites, sites on PHP 8.1 or older and the global services (proxy, database, Redis) aren't recreated. The update needs at least 5 GB of free disk space.
New PHP versions: 8.2 → 8.2.36, 8.3 → 8.3.37, 8.4 → 8.4.28, 8.5 → 8.5.13. Check a site with:
ee shell example.com --command='php -v'PHP sessions stored with PHP's default files handler live inside the site's PHP container, so sessions started before the update are reset when the container is recreated. WordPress itself doesn't use PHP sessions; applications that do will ask their users to log in again.
Disabled sites get their configuration updated during the update and start on the patched image when you enable them with ee site enable example.com.
As with every image update, EasyEngine images that no container uses any more are removed afterwards, including the previous PHP images.
PHP 8.1 and older get no fixes
PHP 8.1 and older are end of life and get no PHP release with these fixes, so v4.14.2 doesn't change them. Move those sites to a supported version, PHP 8.3 or newer, after taking a backup and checking your theme and plugins:
ee site update example.com --php=8.4PHP 8.2 receives security fixes only until December 31, 2026, so plan to move PHP 8.2 sites too.
Docker image updates
| Image | Before | After | Change |
|---|---|---|---|
| easyengine/php8.2 | v4.14.0 | v4.14.2 | PHP 8.2.35 → 8.2.36 (EasyEngine/dockerfiles#386) |
| easyengine/php8.3 | v4.14.0 | v4.14.2 | PHP 8.3.36 → 8.3.37 (EasyEngine/dockerfiles#387) |
| easyengine/php8.4 | v4.14.0 | v4.14.2 | PHP 8.4.27 → 8.4.28 (EasyEngine/dockerfiles#388) |
| easyengine/php8.5 | v4.14.0 | v4.14.2 | PHP 8.5.12 → 8.5.13 (EasyEngine/dockerfiles#389) |
All other images and all command packages are unchanged from v4.14.1.
What's Changed
- chore(release): prepare v4.14.2 #1970 @mrrobot47
- fix(migration): wait up to 180 s for global services during updates #1968 @mrrobot47
- chore(deps): bump php to 8.2.36 in /php/8.2 EasyEngine/dockerfiles#386 @mrrobot47
- chore(deps): bump php to 8.3.37 in /php/8.3 EasyEngine/dockerfiles#387 @mrrobot47
- chore(deps): bump php to 8.4.28 in /php/8.4 EasyEngine/dockerfiles#388 @mrrobot47
- chore(deps): bump php to 8.5.13 in /php/8.5 EasyEngine/dockerfiles#389 @mrrobot47
- fix(php): download only the New Relic agent tarball, not its signature EasyEngine/dockerfiles#384 @mrrobot47