Two critical PHP flaws in versions 8.2 to 8.5 allow code execution without logging in. Fixed in 8.2.35, 8.3.36, 8.4.27 and 8.5.12. Update now.
If your server runs PHP, this week’s job is clear: check your PHP version and update it. These flaws let someone who has no account run commands on your server.
Short answer: two PHP flaws, CVE-2026-109618 and CVE-2026-109619, allow remote code execution without authentication. They affect the PHP 8.2, 8.3, 8.4 and 8.5 branches, and the fixed releases are 8.2.35, 8.3.36, 8.4.27 and 8.5.12. PHP 8.1 and older no longer receive security support, so servers on those branches need to move to a supported version.
At a glance
| Item | Detail |
|---|---|
| CVE | CVE-2026-109618 and CVE-2026-109619 |
| CVSS | CVE-2026-109618: v3.1 9.8, v4.0 9.2. CVE-2026-109619: v3.1 8.1, v4.0 9.2 |
| Flaw type | Memory errors: mishandled out-of-memory handling (109618), and stale memory use after a request ends (109619) |
| Authentication required | No |
| Active exploitation | CISA added both to its KEV catalog on the basis of evidence of active exploitation. Rapid7 reports exploitation attempts |
| CISA KEV added | 26 October 2026 (federal agencies were due to patch by 29 October 2026) |
| Fixed versions | 8.2.35, 8.3.36, 8.4.27, 8.5.12 |
What happened?
PHP handles every web request in its own memory. When memory runs out, PHP uses a special jump mechanism (longjmp) to abort the current request. In CVE-2026-109618, some code paths do not set up memory properly after that abort. The cleanup step that follows can then read that memory or branch on it.
In CVE-2026-109619, PHP’s global state sometimes points into the memory of a request. When that request ends, the global state is not always reset. The next request can then use memory that has already been freed. This class of bug is called use-after-free: the program touches memory after releasing it.
Both flaws can lead to code execution with the privileges of the web server process. The attacker does not need an account on the site.
Who is affected?
- Affected: PHP versions before 8.2.35, 8.3.36, 8.4.27 and 8.5.12. The NVD records also list 8.1 and older in the affected range.
- Affected setups: Every PHP installation that serves web requests. Rapid7 lists PHP-FPM, Apache mod_php, php-cgi, FrankenPHP and LiteSpeed.
- Not affected: Installations running a fixed release or later. Linux distributions can ship a patched package under the old version number, so check your distribution’s security advisory as well as
php -v. - Chain risk: The CISA KEV entry says Linux kernel CVE-2026-46300 can be chained with these flaws to gain root. See our Linux kernel CVE-2026-46300 article. Update the kernel too.
What should you do?
-
Check your version. Run
php -von the command line. The PHP-FPM service that serves your sites can differ from the CLI version. To list PHP services on the server, runsystemctl list-units | grep php. On shared hosting, note the PHP version shown in your control panel. -
Plan a move off unsupported branches. PHP 8.1 reached end of security support on 31 December 2025, so do not wait for a patch on that branch. Move to 8.3, 8.4 or 8.5. Security support for 8.2 ends on 31 December 2026, so plan that move now if you run 8.2. Test your application before switching.
-
Update the package. On Debian and Ubuntu, using your own PHP version in place of 8.3:
sudo apt update
sudo apt install --only-upgrade php8.3-fpm php8.3-cli
On hosting, select PHP 8.2.35, 8.3.36, 8.4.27, 8.5.12 or a later release in the control panel. If the panel shows only the branch, such as “8.3”, ask your provider which patch release is installed.
- Restart the services. Old worker processes keep running the old code. The GHSA advisory recommends restarting all workers:
sudo systemctl restart php8.3-fpm
If you run Apache with mod_php, restart the web server too: sudo systemctl restart apache2.
- If you cannot update right away, apply these interim measures. They do not replace the patch:
- Set
memory_limitto -1, enforce it at the administrative level, and restart the workers. - Set
session.upload_progress.enabled=0in the server-level configuration. A change made in application code comes too late. - If your application does not use multipart form data, block those requests at the front end (web server or WAF). Lower limits such as
post_max_size. - On PHP 8.5, set
fatal_error_backtraces=0. - Do not use
RLIMIT_ASorRLIMIT_DATA. Rapid7 warns that these limits can trigger the vulnerable path.
- Set
Have I been hit?
The sources do not list product-specific file paths or other indicators of compromise. Rapid7 also notes that missing log entries are not proof that a system is safe. Check the following:
- Do your web server access logs show unusually large requests, many multipart form posts, or unexpected error entries?
- Are there PHP files in the web root or in upload folders that you did not put there?
- Have any users, scheduled tasks (cron jobs) or processes appeared recently that you cannot explain?
Rapid7 has published a Velociraptor artifact that inventories PHP installations and running PHP processes. If you find a sign of compromise, consider rebuilding the server from a clean install and rotating database passwords and API keys.
Frequently asked questions
I use hosting. Do I still need to update PHP?
Check the version even if your provider says it has updated PHP. The panel may show only the branch name, so ask your provider for the patch release number if you cannot see it.
I updated my CMS or application. Is that enough?
No. These flaws are in the PHP runtime, so updating an application does not fix them. The PHP version the application runs on must be a fixed release.
I run PHP 8.2. Is 8.2.35 enough?
For these flaws, yes: 8.2.35 and later are fixed. Security support for the 8.2 branch ends on 31 December 2026, though, so plan a move to 8.3 or later soon.
Sources
- NVD: CVE-2026-109618
- NVD: CVE-2026-109619
- GitHub security advisory GHSA-w8hw-w9fx-j79w (CVE-2026-109618)
- GitHub security advisory GHSA-6wmf-4rv5-p3rp (CVE-2026-109619)
- PHP ChangeLog 8.x
- PHP supported versions and PHP end-of-life branches
- CISA KEV: CVE-2026-109618
- Rapid7: analysis of CVE-2026-109618 and CVE-2026-109619
To keep your PHP stack patched and monitored, see our server management service.