What the PHP project released on November 19
On November 19, 2026 the PHP project released PHP 8.6.0, the next feature release of the language. The same day it shipped security updates for every supported branch: PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36. The security team had announced the batch a day earlier, saying it would fix vulnerabilities in all supported versions with a highest severity of critical, and that the critical issues “require either non-default configuration or uncommon setups.”
The November batch follows a more serious round in October. On October 21 the project published a security advisory for two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619, that “can allow unauthenticated remote code execution.” The advisory named PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed as affected, and said it considered the risk highest for mod_php. The fixes are in 8.5.12, 8.4.27, 8.3.36 and 8.2.35. If your host reports a patch number below those, ask them to update this week.
PHP 8.2 security support ends on December 31, 2026
The supported versions page now lists five branches. PHP 8.2 gets security fixes only until December 31, 2026. After that it joins PHP 8.1, which reached end of life on December 31, 2025 according to the project’s end of life table. The other dates to plan around:
- PHP 8.3: security support until December 31, 2027.
- PHP 8.4: active support until December 31, 2026, security support until December 31, 2028.
- PHP 8.5: active support until December 31, 2027, security support until December 31, 2029.
- PHP 8.6: active support until December 31, 2028, security support until December 31, 2030.
The October advisory shows what end of life means in practice. It said PHP 8.1 and older “no longer receive updates from the PHP project.” Because of the severity, the team published minimal source backports for 7.4, 8.0 and 8.1, aimed at people who build PHP from source or have no long-term support vendor. A store on managed hosting cannot apply those itself. From January 1, a store still on PHP 8.2 will be in the same position when the next critical bug is found.
Which PHP version a WooCommerce store should run now
WooCommerce’s server requirements for version 10.8 and later ask hosts for “PHP version 8.3 or greater (tested up to PHP 8.4).” The WordPress PHP compatibility table marks WordPress 7.0 and 7.1 as compatible with PHP 7.4 through 8.5 and does not list PHP 8.6 yet. The WordPress 7.2 Release Candidate 1 post includes “PHP 8.6 compatibility improvements” among the release highlights, and 7.2 is scheduled for December 8.
Our recommendation for a production store today is PHP 8.4. It sits inside WooCommerce’s tested range and keeps security support until the end of 2028. PHP 8.3 works too, but it buys only one more year before you repeat this migration. We would hold off on 8.6 for a live store until WordPress and WooCommerce both list it as tested, and until your payment, shipping and ERP connector plugins have shipped releases that mention it.
What PHP 8.6 changes for store code
The PHP 8.6 release page leads with developer features: partial function application, default values for readonly properties, a clamp() function, a TimeDuration class, a SortDirection enum and an IoPoll API for event loop libraries. These help new code. Older plugins and custom theme code are more likely to be caught by the deprecations and behavior changes listed on the same page:
returninside afinallyblock is deprecated.- The mbstring regex functions, such as
mb_ereg()andmb_split(), are deprecated. - The aliases
is_double(),is_long(),is_integer()anddoubleval()are deprecated, as isspl_object_hash(). session.use_strict_modeandsession.cookie_httponlyare on by default, andsession.cookie_samesitedefaults to Lax.fclose(),file_put_contents()andcopy()now return false when flushing or closing the stream fails.- Many functions throw a
ValueErrorfor out-of-range values, invalid flags or strings containing NUL bytes, where they used to truncate or ignore them silently.
Deprecations only write notices to the log. The ValueError change behaves differently: code that used to pass a bad value and carry on will now stop with a fatal error. The session defaults matter for bespoke code that uses PHP’s native sessions, for example an old B2B login bridge or a payment return handler written years ago. The release page links to the migration guide in the PHP manual, which lists every change in detail.
What to do before the end of the year
This is the order we would work in for a store that is on PHP 8.2 or older today:
- Find the current PHP version and patch number in your hosting panel, or in WordPress under Tools, Site Health, Info, Server.
- If the patch number is below the October fixes, ask your host to apply them now, whatever the branch.
- Clone the store to staging and switch staging to PHP 8.4 with debug logging turned on.
- Place test orders with every payment method, issue a refund, and let your ERP or inventory sync complete a full cycle.
- Read the debug log for deprecation notices and fatal errors, and send anything that comes from a third-party plugin to its vendor.
Many stores freeze changes from late November through the holidays. If that is your policy, book the production switch for the first quiet week of December, once staging passes, so the store is on PHP 8.4 before 8.2’s security support ends on December 31.





