PHP CVE-2026-109618 and CVE-2026-109619: How to Check and Patch Your Site Today
Two critical PHP runtime flaws are being exploited in the wild. Here's how to check whether your site is affected and patch it properly.
Two critical flaws in PHP itself, CVE-2026-109618 and CVE-2026-109619, are being exploited in the wild. They sit in the PHP runtime, not in WordPress or your code, so updating plugins won't fix them.
Short answer: upgrade PHP to 8.2.35, 8.3.36, 8.4.27 or 8.5.12 (or your host's patched package), then restart PHP-FPM or Apache. If you're on PHP 8.1 or older, there's no official fix. You need to upgrade the PHP branch, or get a backported build from your host.
Why this problem exists
PHP released fixes for both flaws on 21 October 2026. PHP rates both CVSS v4.0 9.2 (Critical). Within days, CISA added both to its Known Exploited Vulnerabilities catalog, and security firms reported attacks in the wild. Some attempts were seen before the fix was even published.
Two things make this worse than a typical PHP bug:
- It's in the runtime. Every site on an unpatched PHP binary is exposed, whatever CMS it runs.
- Updating the package isn't enough. PHP-FPM pools and Apache with mod_php keep the old code in memory until they restart. It's common to find servers that show the "new" version in the package manager while still running the vulnerable one.
| PHP branch | Vulnerable | Fixed in |
|---|---|---|
| 8.5 | before 8.5.12 | 8.5.12 |
| 8.4 | before 8.4.27 | 8.4.27 |
| 8.3 | before 8.3.36 | 8.3.36 |
| 8.2 | before 8.2.35 | 8.2.35 |
| 8.1 and older | yes | no official release (backports only) |
The solution — the Hitori PHP patch path
Step 1: Find the PHP version your site actually runs
The CLI version and the web version are often different. Check what the website is using:
<?php echo PHP_VERSION, ' / ', PHP_SAPI;
Upload that as version-check.php, open it in a browser, note the result, then delete the file. On shared hosting, cPanel's "Select PHP Version" or MultiPHP Manager shows the same thing.
On a server you can also run:
php -v
php-fpm8.3 -v # or whichever FPM version you run
Step 2: Patch the runtime
Ubuntu / Debian (Ondřej Surý PPA or distro packages):
sudo apt update
sudo apt install --only-upgrade 'php8.3*'
RHEL / AlmaLinux / Rocky (Remi):
sudo dnf upgrade 'php*'
Docker: rebuild from the patched official image tag (for example php:8.3.36-fpm), then redeploy. Don't just restart the old container.
Shared hosting: ask your host for the exact patched version number. "We're up to date" isn't an answer.
Step 3: Restart every PHP process
sudo systemctl restart php8.3-fpm
sudo systemctl restart apache2 # if you use mod_php
Restart queue workers, Laravel Horizon, Supervisor jobs and any other long-running PHP process too.
Step 4: Verify
Load version-check.php again and confirm the patched version, then delete it.
Step 5: Check for compromise
Attacks started before disclosure, so patching alone isn't proof you're clean. From 17 October 2026 onwards, look for:
- PHP-FPM or Apache worker processes starting shells (
sh,bash) or download tools (curl,wget) - New or recently changed
.phpfiles in upload folders and other writable directories - New admin users in your CMS
- Unexpected cron jobs and outbound connections
find /var/www -name "*.php" -newermt "2026-10-17" -print
If you can't patch today
These reduce exposure but do not make the server safe. Treat them as hours-long stopgaps, not a fix:
- For CVE-2026-109618: set
memory_limit=-1at the server level, keeppost_max_sizelow, and limit request size at Nginx, Apache or your proxy. - For CVE-2026-109619: set
session.upload_progress.enabled=0inphp.inior the FPM pool config (notini_set()or.user.ini), then restart every worker. On PHP 8.5, also setfatal_error_backtraces=0. - Put the site behind a WAF, or take it offline if it holds sensitive data.
Remember to undo memory_limit=-1 once you've patched. Left in place, one bad script can take down the server. Our guide to the PHP "allowed memory size exhausted" error explains how to set limits properly.
Fix options compared
| Situation | Best fix | Time | Risk |
|---|---|---|---|
| PHP 8.2–8.5 on your own server | Package upgrade + restart | 15–30 min | Low |
| Shared hosting | Ask host for patched build, confirm the version | Hours to days | Depends on host |
| PHP 8.1 or older | Upgrade the branch to 8.3/8.4 | 1–5 days with testing | Medium: code may break |
| Can't touch the server | WAF + config workarounds | Minutes | High: not a fix |
Common mistakes and how to avoid them
- Updating WordPress instead of PHP. This is a runtime bug. Your CMS version doesn't matter.
- Not restarting PHP-FPM. The package says patched, but the running process isn't.
- Checking
php -vonly. The CLI can be patched while the website uses a different FPM version. - Forgetting old PHP versions that are still installed and assigned to one forgotten site.
- Upgrading from 7.4 straight to 8.3 on live. Test on staging first. Our guide to PHP 8 upgrade errors covers what usually breaks.
Real-world example
A typical case: a small business site on a VPS running PHP 8.1 for "compatibility", with an old theme that nobody wants to touch. 8.1 gets no official fix, so the only real option is an upgrade.
The safe sequence is: clone the site to staging, switch staging to PHP 8.3.36, fix the deprecation and fatal errors it throws, test checkout and forms, then switch live and restart FPM. On a typical brochure or WooCommerce site this takes about a day, most of it testing.
Troubleshooting checklist
- ☐ Web-facing PHP version confirmed as a patched release
- ☐ PHP-FPM, Apache and workers restarted
- ☐ No old PHP versions still assigned to any site
- ☐ Writable folders checked for new
.phpfiles since 17 October - ☐ CMS admin users reviewed
- ☐ Temporary workarounds removed after patching
- ☐ Plan in place to leave PHP 8.2 before it reaches end of life on 31 December 2026
Frequently asked questions
Is WordPress affected? Yes, if it runs on an unpatched PHP version. The flaws are in PHP, so any PHP application can be exposed.
I'm on PHP 7.4. Am I safe? No. Researchers say older releases are affected too, and 7.4 gets no official fix. Upgrade the PHP branch.
Does a firewall like Cloudflare protect me? It can block some attacks, but Cloudflare itself says you still need to patch.
How do I know if I was hacked? Look for web processes starting shells, new PHP files in upload folders, new admin users and unknown cron jobs since 17 October. If you find any, assume compromise and restore from a clean backup after patching.
Sources: PHP supported versions, Rescana advisory summary.
Get a fixed-price quote
Tell us what's broken or what you need. We reply within one working day with a price and timeline. No obligation.
Need it done today? Our PHP security fix service patches your server within 24 hours, with a malware scan included. Or fill in the form above for a fixed-price quote.