Security News

PHP Patches 18 Flaws, Seven Critical, a Month After 'PHP2Shell' Attacks Hit Real Systems

Infosecurity Magazine · 20 Nov 2026
Key Takeaway Check which PHP version your websites and applications run, and schedule the upgrade to a patched release now rather than waiting for the next maintenance window.

The PHP Foundation has released security patches for 18 newly disclosed vulnerabilities, seven of which are rated critical. The flaws affect all supported PHP versions, although the source notes that exploiting them requires either non-default configuration or uncommon setups.

The update arrives a month after two critical flaws, CVE-2026-109618 and CVE-2026-109619, collectively known as 'PHP2Shell', were disclosed. Those were not just a theoretical risk. Check Point reported campaigns exploiting PHP2Shell against its own security gateways dating back to 30 October, involving backdoors and destructive tools aimed at VMware ESXi virtualisation servers. Attackers also targeted Palo Alto Networks firewalls whose administrative interfaces were exposed to the internet.

One of the new critical flaws, dubbed 'PHPAfterShell' (CVE-2026-126714), was found by security firm Depthfirst using AI models tuned for cybersecurity tasks. It sits in PHP's session handling with file-based storage, which is the default setting (session.save_handler = files). By manipulating a session while a file is being uploaded, an attacker could potentially trick the server into running arbitrary code. That could expose login credentials and customer records, allow session data to be changed, let attackers spy on visitors or disrupt the service. A separate remote code execution flaw in session upload progress (CVE-2026-115560) was also disclosed, though exploitation is said to need a highly specific and unlikely combination of conditions.

The fixes ship in PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13 and 8.6, released on 19 November as part of the regular four-week cycle. Downstream projects are responding: FrankenPHP is working with The PHP Foundation and Docker on updated builds, and Laravel said it is preparing a remediation plan for applications on its hosting and deployment services.

Why it matters

The PHPAfterShell flaw sits in the default file-based session handler, which breaks the assumption that default settings are the safe baseline, even though the source says overall exploitation needs unusual setups. With PHP2Shell already used against internet-facing gateways and firewalls, anyone running PHP on exposed systems has seen how quickly disclosure turns into attacks. Businesses that rely on hosting providers or frameworks must now confirm who is responsible for applying the patched builds.

What to do

  • Upgrade PHP to a fixed release: 8.2.36, 8.3.37, 8.4.28, 8.5.13 or 8.6.
  • Confirm whether your hosting provider or framework vendor, such as Laravel or FrankenPHP, has shipped updated builds.
  • Check that PHP2Shell fixes (CVE-2026-109618 and CVE-2026-109619) were applied on internet-facing systems.
  • Remove internet exposure of administrative interfaces on firewalls and gateways.

Summarised by CISO AI from Infosecurity Magazine, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.