All CVEs

PHP2Shell (CVE-2026-109618/109619): unauthenticated RCE in PHP, exploited in the wild and in CISA KEV. If PHP serves web traffic (mod_php, FPM, CGI), update to 8.6.0, 8.5.13, 8.4.28, 8.3.37 or 8.2.36 (19 Nov) and restart workers. 8.1 and older: no official fix. https://tldrcve.com/php2shell/

PHP · CVE-2026-109618 · CVE-2026-109619

PHP2Shell

Patch nowExploited in the wild. In CISA KEV.

Two bugs in PHP itself let an attacker with no login run code on web servers that run PHP. Attacks are already happening, so if you serve PHP on the web, update now.

How scary is it?

updated 20 Nov
  • Yes: Works without logging in1,2,3
  • Yes: Public exploit code is out9,7
  • Yes: Attacks seen in the wild4,6,7
  • Yes: On CISA's exploited list (since 26 Oct)4

Scare-o-meter

Drop everything

Attackers are already on it.
Patch now.

Are you affected? only if all are true

1PHP older than 8.2.35 / 8.3.36 / 8.4.27 / 8.5.12command

Or any end-of-life branch (8.1 and older), or patched but workers not restarted since. Check the runtime that serves the web, not just the CLI. Distros may backport the fix without changing the version number.1,5

php -v
php-fpm -v
2PHP serves web requestscommand

Via mod_php, PHP-FPM, php-cgi, FrankenPHP or LiteSpeed. Full exploitation has been shown on Apache mod_php, and for CVE-2026-109619 also on PHP-FPM. Command-line-only use isn't in scope.1,2,3

apachectl -M | grep php

What to do

1Update and restart PHP

Update to 8.6.0, 8.5.13, 8.4.28, 8.3.37 or 8.2.36 (19 Nov 2026), then restart all workers. These include the 21 Oct PHP2Shell fixes plus newer security fixes. 8.1 and older get no official release; use a vendor with long-term support or upgrade.1,8,10

Latest safe versions checked 20 Nov

PHP → 8.68.6.08.58.5.138.48.4.288.38.3.378.28.2.36PHP 8.1 and older get no fixes from PHP. Distros may backport fixes without changing the version number.
2Can't update yet? Change these settingscommand

Not a full fix, per PHP. Set them in php.ini or the FPM pool config, not with ini_set(), then restart. On PHP 8.5 also set fatal_error_backtraces = 0. Keep a container or cgroup memory limit, because memory_limit = -1 removes PHP's own cap.1,2,3

session.upload_progress.enabled = 0
memory_limit = -1

This page shows you how to check. It can't tell you you're safe.

Sources (11) and changelog
  1. PHP: release announcements and advisory 21 Oct
  2. PHP GHSA: CVE-2026-109618
  3. PHP GHSA: CVE-2026-109619
  4. CISA KEV: added 26 Oct 26 Oct
  5. Pentest-Tools: version checks, backport caveat
  6. BleepingComputer: attacks confirmed
  7. Wiz: exploitation so far 27 Oct
  8. PHP: 8.x ChangeLog, 19 Nov 2026 releases 19 Nov
  9. BleepingComputer: public exploit worked on a single-worker mod_php setup 26 Oct
  10. PHP: 8.6.0 ChangeLog 19 Nov
  11. php-src: 19 Nov security advisories (eight rated Critical)