Security fix for CERT-EU 2026-018: PHP CVE-2026-109618 / CVE-2026-109619, unauthenticated RCE, PHP < 8.3.36. The recipe uses mod_php, which the advisory rates highest risk.
Image:wordpress:7.1.3 was rebuilt upstream on PHP 8.3.36 (new digest sha256:30c76f0a…). The tag is unchanged, so this bumps the recipe to 4.1.2+7.1.3 so that deploying it pulls the patched image.
Mitigation:session.upload_progress.enabled = Off in uploads.ini.tmpl (PHP_UPLOADS_CONF_VERSION v4 → v5). This blocks the confirmed CVE-2026-109619 session path as defence in depth. WordPress doesn't use this feature.
Security fix for [CERT-EU 2026-018](https://cert.europa.eu/publications/security-advisories/2026-018/): PHP CVE-2026-109618 / CVE-2026-109619, unauthenticated RCE, PHP < 8.3.36. The recipe uses `mod_php`, which the advisory rates highest risk.
**Image:** `wordpress:7.1.3` was rebuilt upstream on PHP 8.3.36 (new digest `sha256:30c76f0a…`). The tag is unchanged, so this bumps the recipe to `4.1.2+7.1.3` so that deploying it pulls the patched image.
**Mitigation:** `session.upload_progress.enabled = Off` in `uploads.ini.tmpl` (`PHP_UPLOADS_CONF_VERSION` v4 → v5). This blocks the confirmed CVE-2026-109619 session path as defence in depth. WordPress doesn't use this feature.
**Tested on cc-test**
- Upgrade 4.1.1 → 4.1.2: config v4 → v5, upload progress on → off, healthy
- Fresh install + `core_install`: PHP 8.3.36 (`apache2handler`), admin login, media upload through `async-upload.php`
- Backup → undeploy + delete volumes → redeploy → restore with hooks: marker post and uploaded file both came back
**Operators:** after deploying, check the PHP version with `abra app run <domain> app -- php -v` (should print 8.3.36).
cc @trav @notplants
PHP 8.3.35 in wordpress:7.1.3 is vulnerable to CVE-2026-109618 and
CVE-2026-109619. The real fix is the rebuilt official image on PHP
8.3.36; this disables the confirmed session upload-progress exploit
path as defence in depth and bumps the version so operators redeploy
and re-pull the image.
autonomic-bot
requested review from trav 2026-10-21 19:03:31 +00:00
autonomic-bot
requested review from notplants 2026-10-21 19:03:31 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Security fix for CERT-EU 2026-018: PHP CVE-2026-109618 / CVE-2026-109619, unauthenticated RCE, PHP < 8.3.36. The recipe uses
mod_php, which the advisory rates highest risk.Image:
wordpress:7.1.3was rebuilt upstream on PHP 8.3.36 (new digestsha256:30c76f0a…). The tag is unchanged, so this bumps the recipe to4.1.2+7.1.3so that deploying it pulls the patched image.Mitigation:
session.upload_progress.enabled = Offinuploads.ini.tmpl(PHP_UPLOADS_CONF_VERSIONv4 → v5). This blocks the confirmed CVE-2026-109619 session path as defence in depth. WordPress doesn't use this feature.Tested on cc-test
core_install: PHP 8.3.36 (apache2handler), admin login, media upload throughasync-upload.phpOperators: after deploying, check the PHP version with
abra app run <domain> app -- php -v(should print 8.3.36).cc @trav @notplants
!testme
🌻 cc-ci —
wordpress@7fc19b62✅ passedfull logs · dashboard
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.