Skip to content

Add mitigations for CVE-2026-109618 and CVE-2026-109619 - #1022

Closed
Mr-Alidoosti wants to merge 1 commit into
docker-library:masterfrom
Mr-Alidoosti:fix/cve-2026-109618-109619-mitigations
Closed

Mr-Alidoosti wants to merge 1 commit into
docker-library:masterfrom
Mr-Alidoosti:fix/cve-2026-109618-109619-mitigations

Conversation

@Mr-Alidoosti

Copy link
Copy Markdown

Summary

This PR applies official recommended security mitigations for the critical unauthenticated Remote Code Execution vulnerabilities announced on 21 Oct 2026:

Advisory reference: https://www.php.net/archive/2026.php#2026-10-21-5

Changes

In $PHP_INI_DIR/conf.d/security-mitigations.ini across all web variants (Apache & FPM):

  1. Stale Global State Mitigation (CVE-2026-109619):
    • Sets session.upload_progress.enabled = 0.
    • On PHP 8.5, also sets fatal_error_backtraces = 0.
  2. OOM Corruption Mitigation (CVE-2026-109618):
    • Sets memory_limit = -1 to eliminate controllable PHP internal memory limit aborts.
    • Sets conservative request boundaries suitable for WordPress: post_max_size = 32M and upload_max_filesize = 30M.

CLI variants (wp-cli) do not serve web requests and remain unchanged.

Generated via ./apply-templates.sh.

Official PHP security advisory released on 21 Oct 2026 reports two critical
unauthenticated Remote Code Execution vulnerabilities:

1. CVE-2026-109618 (RCE via OOM corruption):
   - Out-of-memory handling can interrupt PHP while internal request data
     is only partially initialized.
   - Mitigation: set 'memory_limit = -1' to avoid controllable PHP internal
     OOM failure, with conservative 'post_max_size = 32M' and 'upload_max_filesize = 30M'.

2. CVE-2026-109619 (RCE via stale global state):
   - Request-owned internal state can survive after its backing memory has
     been freed, allowing subsequent requests handled by the same worker
     to reuse stale state.
   - Mitigation: disable 'session.upload_progress.enabled = 0', and for PHP 8.5
     set 'fatal_error_backtraces = 0'.

Ref: https://www.php.net/archive/2026.php#2026-10-21-5
GHSA: GHSA-w8hw-w9fx-j79w, GHSA-6wmf-4rv5-p3rp
@XVII

XVII commented Oct 21, 2026

Copy link
Copy Markdown

The new wordpress image builds will be done soon; these mitigations do not make the image safe.

@meirka

meirka commented Oct 21, 2026

Copy link
Copy Markdown

Um. why do you need mitigation when you have fix from PHP?

@dunklesToast

Copy link
Copy Markdown

Isn't the obvious solution to bump php to the patched versions? Also, your changes do not make the image safe. From the PHP News Archive:

the following measures reduce exposure to specific attack paths but do not make an installation safe

@Mr-Alidoosti
Mr-Alidoosti deleted the fix/cve-2026-109618-109619-mitigations branch October 21, 2026 15:53
@tkn777

tkn777 commented Oct 21, 2026

Copy link
Copy Markdown

Hey guys, German mainstream media are already reporting on the issue. Companies and organizations have already taken their websites offline. The matter is quite urgent. Thanks for your efforts!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants