PHP Warns of Critical Security Flaws Affecting All Supported Versions, Urges Users to Update

Blog WriterCybersecurity News - Original News Source is cybersecuritynews.com


The PHP security team has warned of vulnerabilities across all branches covered by its November 19, 2026 security update, with the most severe issues rated critical.

The team urged website operators and hosting providers to update promptly. It also made an important distinction: the critical flaws require non-default settings or uncommon setups, so not every installation faces the same risk.

The November security releases are PHP 8.5.13, 8.4.28, 8.3.37, and 8.2.36. These are updates for existing PHP branches, so administrators can patch without moving applications to a new branch. The advance notice set a release window of 14:00 to 14:30 UTC and said the updates were part of PHP’s regular four-week release cycle.

As Cyber Security News noted in its earlier coverage of the PHP warning, the release window fell on the planned launch date for PHP 8.6.0. The two events serve different purposes. Teams that need to close security gaps can patch the branch they already run without rushing a move to PHP 8.6.

PHP Security Update Covers

One issue PHP flagged before the November release is CVE-2026-115560, a remote code execution flaw tied to session upload progress. The feature lets an application track a file upload while it is still underway.

PHP said the flaw only affects an unusual combination of application behavior and server settings. Remote code execution means an attacker could run code on the server.

PHP advised administrators with affected setups to temporarily disable upload progress by setting session.upload_progress.enabled=0. The project said applications that never change how PHP stores session data while the code is running can leave the feature enabled. That advice applies to the upload progress flaw, not to every issue in the November update.

The PHP security team’s advance notice did not name every flaw or assign a severity to each one. Administrators should use the PHP 8 changelog to check which fixes apply to their branch rather than assume that every flaw affects every setup.

Start with internet-facing services, then check background jobs, container images, and deployment pipelines for older PHP copies. Install the update for your branch through your usual package source or ask your hosting provider when its patched build will be available. If your provider applies fixes without changing the main PHP version number, check its security notice before judging patch status.

Restart PHP workers after patching and verify the version serving live web requests. Checking php -v alone only confirms the command-line version. If you run PHP in containers, rebuild and redeploy the image so new instances do not start with the old runtime.

The new updates follow October’s PHP2Shell emergency patches for CVE-2026-109618 and CVE-2026-109619. Those are separate bugs that could let attackers run code without signing in. The CISA alert on PHP2Shell covers the October flaws, not the November batch. An October update should not be treated as proof that a server has the November fixes.

PHP 8.2 users have a second deadline: the branch reaches end of life on December 31, 2026. Apply the November patch now, then test a move to a newer supported branch before PHP 8.2 stops receiving security fixes from the project.

What Are Leading Organizations Doing About AI and Cyber Risks? Find Out. View Details!

The post PHP Warns of Critical Security Flaws Affecting All Supported Versions, Urges Users to Update appeared first on Cyber Security News.