← All articles

PHP security flaws set for critical fixes on November 19

PHP security flaws set for critical fixes on November 19

PHP security flaws affecting all supported versions are due to be addressed in a security release scheduled for November 19, 2026, between 2 and 2:30 p.m. UTC. The PHP maintainers said the release is part of the programming language’s regular four-week release cycle and that its highest-severity issues are rated critical.

A critical rating does not mean every PHP installation is automatically exposed. The maintainers said the critical issues require either a non-default configuration or an uncommon setup, but they did not publish further details about those conditions in the initial advisory. Users are advised to install the updates as soon as they become available.

The planned release is expected to include CVE-2026-115560, a remote code execution vulnerability. Remote code execution means an attacker may be able to make a vulnerable system run commands of the attacker’s choice. The flaw works only when several conditions are present at the same time.

First, an application must set the session.serialize_handler option to php_binary or php_serialize in its configuration, then change the handler to php with ini_set() before calling session_start(). Sessions are the files or stored records that help a website remember a visitor between requests. Second, session upload progress must be enabled. The source states that this feature is enabled by default in PHP.

Until the next regular bugfix release, users were urged to set session.upload_progress.enabled=0. After changing that setting, the PHP worker must be restarted so the new configuration takes effect. A PHP worker is the background process that handles PHP requests for a website. Website owners who cannot change these settings themselves should ask their hosting or IT provider whether the affected configuration is in use and whether the temporary mitigation has been applied.

The announcement follows fixes released nearly a month earlier for CVE-2026-109618 and CVE-2026-109619. Together tracked as PHP2Shell, those vulnerabilities enable unauthenticated remote code execution through specially crafted HTTP requests. Unauthenticated means the attacker does not need to log in first.

The PHP2Shell flaws have seen limited active exploitation. The attacks targeted publicly accessible Palo Alto Networks management interfaces and Check Point Security Gateways, then used those systems to attack Active Directory and deliver backdoors. Active Directory is a system organisations use to manage user accounts, computers and access within a network. A backdoor is hidden access that can let an attacker return to a compromised system.

Hunt.io reported on October 30, 2026, that it had identified 616 PHP2Shell-related files across multiple hosts. The files included shared exploit kits, cloned proof-of-concept programs, custom heap exploits, scanners and post-exploitation tools. Proof-of-concept code demonstrates how a vulnerability can be exploited, while post-exploitation tools are used after an attacker has gained access. Hunt.io also described underground forum participants seeking exploits, discussing prerequisites and debating whether circulating proof-of-concept code worked.

CrowdStrike said exploit developers are unlikely to produce one universal exploit that works reliably against every affected PHP deployment. That does not remove the need to patch. Different PHP applications and configurations may behave differently, and the absence of a universal exploit does not show that an individual installation is safe.

PHP also patched a separate critical vulnerability in Brotli last month. Tracked as CVE-2026-111497 and also called Node2Shell or Broccoli2Shell, it is an out-of-bounds write in the decoder library. An out-of-bounds write occurs when software writes data outside the memory area reserved for it, which can corrupt a process and, in this case, could lead to arbitrary code execution.

For WordPress site owners, AEU Hosting provides managed WordPress hosting secured end to end, which can help reduce the burden of managing the hosting environment while PHP security updates are released.

Administrators should apply the November 19 updates as soon as they are available, confirm that the PHP worker has restarted after any mitigation change and review whether applications use the session settings described above. They should also treat publicly accessible management interfaces as a priority for patching and monitoring, particularly where Active Directory access is involved.

Also available in: DeutschItalianoShqip