If your company website, online store or internal system runs on PHP, WordPress sites included, ask your host or team today to update PHP to one of the releases published on November 19, 2026: 8.5.13, 8.4.28, 8.3.37 or 8.2.36. Depending on the branch, the update fixes up to 18 vulnerabilities, some of which the PHP project rates critical. And if your site is on PHP 8.2, you have only 41 days left: after December 31, 2026 it gets no security fixes at all. This follows our article on the upload progress flaw, which this update finally fixes.
What was released on November 19?
On November 18 the PHP security team posted advance notice of security releases the next day between 14:00 and 14:30 UTC, that is 5:00 to 5:30 pm Riyadh time, as part of its regular 4-week release cycle. The notice said the highest severity is critical, and that the critical issues require non-default configuration or uncommon setups. On November 19 the releases shipped, and we counted the CVE-numbered fixes in the official changelog for each branch:
| Branch | Safe release | Vulnerabilities fixed |
|---|---|---|
| PHP 8.5 | 8.5.13 | 18 |
| PHP 8.4 | 8.4.28 | 14 |
| PHP 8.3 | 8.3.37 | 13 |
| PHP 8.2 | 8.2.36 | 12 |
PHP 8.6.0 also came out the same day. It is a new feature release, not a security update, so do not confuse the two: what you need now is the update within the branch you already run.
Which flaws matter most, and is your site exposed?
- CVE-2026-129289 in PHP-FPM, rated 9.2: according to PHP's advisory on GitHub, an attacker without a password can run code on the server with a single request, but only if the web server reuses the same connection to PHP-FPM, for example fastcgi_keep_conn on in Nginx or enablereuse=on in Apache. A standard setup that closes the connection after each request is not exposed to the published attack.
- CVE-2026-115560 in sessions: the flaw the project announced on October 23 without a fix now has a final one. The temporary measure (session.upload_progress.enabled = 0) is still useful, but it does not cover the other flaws.
- Other flaws that can lead to code execution: memory bugs in the PHP engine, the timezone cache and session files, plus a signature bypass in PHAR files, according to Aikido's analysis and BleepingComputer.
As of November 20, neither PHP's announcements nor the reports we reviewed mention active exploitation of these flaws. But October's PHP2Shell flaw showed that attacks can start within days of disclosure, so do not wait.
PHP 8.2 support ends on December 31
This is the decision that matters most for a business owner. According to the supported versions table on the PHP site, security support for each branch ends on these dates:
- PHP 8.2: until December 31, 2026.
- PHP 8.3: until December 31, 2027.
- PHP 8.4: until December 31, 2028.
- PHP 8.5: until December 31, 2029.
- PHP 8.6: until December 31, 2030.
The October 21 announcement confirmed that PHP 8.2 receives no security fixes after that date. Version 8.1 and older are already out of support, and the project issues no fix for them for these flaws. Moving to 8.3 or 8.4 may require testing old plugins and themes, so start now, not in the last week of December.
What to ask your host or team this week
- The PHP version on every site and system you own, including old sites and staging sites.
- Written confirmation that the November 19 fixes are applied and PHP processes were restarted. On Linux servers the version number may differ, because distributions add the fix to their own package.
- A clear answer: does the web server reuse connections to PHP-FPM? If yes and the update is not applied yet, turning off connection reuse temporarily closes the published attack path for the most serious flaw.
- A plan and a date to move from PHP 8.2 or older to 8.3 or newer before December 31, with a backup before the move.
- Confirmation that PHP-FPM ports are not exposed directly to the internet.
The Origami view
Three PHP security updates in one month say something plain: a website is not a project that ends on launch day. Many Saudi businesses own a site built years ago on hosting nobody in the company knows who manages, and those are exactly the sites that stay on 8.1 or 8.2 until something happens.
Our advice is to give every site or system a named owner and a simple record of its version and last update date. If you want someone to review this with you or move your site to a supported version, contact us.
The bottom line
Update PHP today to 8.5.13, 8.4.28, 8.3.37 or 8.2.36, and get written confirmation from your host. If you are on 8.2 or older, put a migration date before December 31, 2026 on this month's calendar, because after it come flaws with no fix.
Sources
- PHP: upcoming critical security release notice, November 18, 2026
- PHP: releases 8.5.13, 8.4.28, 8.3.37 and 8.2.36, November 19, 2026
- PHP: official PHP 8 changelog
- PHP on GitHub: advisory for CVE-2026-129289 in PHP-FPM
- PHP: supported versions table
- PHP: October 21, 2026 announcement and PHP 8.2 end of life
- Aikido: analysis of the November 19, 2026 release
- BleepingComputer: PHP security updates fix 18 flaws
Frequently asked questions
Which version should I update PHP to now?
Stay on your branch and update to its latest release: 8.5.13, 8.4.28, 8.3.37 or 8.2.36, all released on November 19, 2026. If you are on 8.2, plan a move to 8.3 or newer before December 31, 2026.
My site runs WordPress. Is updating WordPress and its plugins enough?
No. Updating WordPress does not update the PHP running underneath it. The PHP version is managed by your host or whoever runs the server, so ask them for written confirmation of the version and that the November 19 fixes are applied.
What happens if my site stays on PHP 8.2 after December 31?
The site keeps working, but any flaw found after that date gets no official fix from the PHP project, so the site stays exposed to it. That is why the project advises moving to a supported branch.
Are these flaws being exploited?
As of November 20, 2026, neither PHP's announcements nor the reports we reviewed mention active exploitation. But the PHP2Shell flaws in October were attacked within days of disclosure, so it is better to update now.







