PHP Vulnerability 2026
-
Thursday, 22nd October, 2026
-
07:36am
PHP has released emergency security updates on October 21, 2026, to address two critical, unauthenticated Remote Code Execution (RCE) vulnerabilities (CVE-2026-109618 and CVE-2026-109619) with a CVSS score of 9.2.
Patched Versions
You should immediately upgrade your PHP environment to one of the following safe versions:
- PHP 8.5 ➔ Update to 8.5.12
- PHP 8.4 ➔ Update to 8.4.27
- PHP 8.3 ➔ Update to 8.3.36
- PHP 8.2 ➔ Update to 8.2.35
Critical Notes
- Unsupported Versions: PHP 8.1 and below are End-of-Life (EOL) and will not receive official updates. If you cannot upgrade to a supported PHP version immediately, check with your OS distributor or hosting provider for backported patches (e.g., via cPanel, Remi repository).
- Application Updates Won't Help: This is a core PHP infrastructure vulnerability affecting PHP-FPM, mod_php, php-cgi, LiteSpeed, and FrankenPHP. Updating application-level code like WordPress or Laravel plugins will not fix this issue; you must patch the PHP binary on your server.
- Active Exploitation: Scan activity targeting these vulnerabilities has been detected in the wild. Please back up your data and perform the update as soon as possible.
According to the official PHP Security Advisory and vendor notices,
there is no complete configuration workaround that makes your server entirely safe. Only a full binary upgrade provides complete protection.
However, if you absolutely cannot update immediately, you can implement the following interim configuration changes to reduce exposure to the primary confirmed attack paths:
1. Mitigating CVE-2026-109619 (Stale Global State / Session Processing)
Attackers are primarily targeting the session upload progress handler to trigger this bug.
- Disable Session Upload Progress: Open your
php.ini or PHP-FPM pool configuration and set:
session.upload_progress.enabled = 0
(Note: You must apply this at the system level before request parsing. Do not rely on ini_set() inside application code as it runs too late.)
- Disable Fatal Error Backtraces (PHP 8.5 only): If you are running early versions of PHP 8.5, also add:
fatal_error_backtraces = 0
- Restart Workers: You must restart PHP-FPM, Apache, or your web worker processes for these changes to take effect.
2. Mitigating CVE-2026-109618 (Out-of-Memory Corruption)
This vulnerability triggers when PHP runs out of memory during early request processing.
- Remove PHP's Internal Memory Limit: Set the internal memory limit to unlimited to avoid triggering controllable PHP memory failures:
Warning: To prevent malicious memory exhaustion on the host, you must substitute this by enforcing strict OS-level container or cgroup memory limits to kill the affected worker if necessary. Do not use
RLIMIT_AS or RLIMIT_DATA as they will re-trigger the vulnerable path.
- Restrict Request Sizes: Constrain input sizes so large payloads cannot trigger memory failures:
post_max_size = 8M (or 32M if file uploads are required)
upload_max_filesize = 8M
- Enforce Web Server/Proxy Limits: If using Nginx, Apache, or a reverse proxy (like Cloudflare), strictly enforce limits on incoming request sizes, maximum header sizes, multipart counts, and form-field counts before they even reach PHP.
3. Clean up Error Configurations
- Remove any invalid or deprecated settings applied per-request that emit warnings or notices before initialization.
- Silencing diagnostics using
error_reporting, display_errors, or @ does not prevent the vulnerability from being exploited.