CyberKit

Threat intel / Exploited vulnerabilities

PHP2Shell: two PHP core flaws, emergency patches out

PHP fixed two core flaws on 21 October that can allow code execution without a login. CISA added both to its exploited list on 26 October, and Amazon says targeting began before the patches.

High severity. Active. Moderate confidence. First reported 21 Oct 2026, last activity 26 Oct 2026. Briefing updated 28 Oct 2026.

AI-written summaries of public reporting, each checked against at least two sources from different publishers. Check the sources before you act. Last refreshed 2026-11-18 14:09 UTC. How this is made.

What is not settled: The PHP advisory, Vercel's bulletin, CISA's pages and BleepingComputer could not be opened during this refresh, so the 26 October catalog addition and Amazon's timeline come from search results and secondary coverage. That is why confidence stays moderate. CISA Known Exploited Vulnerabilities status is not checked against the catalog, so kev is left out. A Vulmon audit disputes the second flaw. A vendor claim that the flaw affects most of the internet is not used.

In plain words

What happened

PHP is the language many websites run on, and it has two serious flaws in its core code. Someone who can reach a PHP site over the internet may be able to run commands on the server without logging in. The PHP project released fixed versions on 21 October.

Who is behind it

No group has been named publicly. Amazon describes the early targeting, but reporting does not say who was behind it.

What they want

Nothing public says yet. Early activity looks like searching for servers that can be taken over, which could lead to defacement, data theft, or a foothold for later attacks.

What they did

Amazon Threat Intelligence says attackers were targeting the flaws four days before the patches shipped. CISA added both to its Known Exploited Vulnerabilities list on 26 October, with a federal deadline of 29 October, according to press coverage. Researchers also report exploit attempts, and some public exploit code is reported to exist.

Who is at risk

Any website or server running an unpatched PHP build and reachable from the internet. Shared hosting, self-hosted content systems and custom PHP applications are the most exposed.

What to do

  • Upgrade PHP to 8.5.12, 8.4.27, 8.3.36 or 8.2.35, or the patched build from your hosting provider.
  • Do not rely on a web application firewall alone. Upgrade the PHP runtime itself.
  • Review web server logs for unusual requests to PHP endpoints since 21 October, and treat any hit as an incident until you have ruled it out.
The technical version, for hunting and patching

What happened

PHP core advisories for CVE-2026-109618 and CVE-2026-109619, both rated CVSS v4.0 9.2. Crafted HTTP requests may allow remote code execution, data exposure, or denial of service. Fixed releases are 8.5.12, 8.4.27, 8.3.36 and 8.2.35.

Who is behind it

No named actor. Amazon Threat Intelligence reports targeting before the patches, Watchtowr reports exploitation in its honeypot network, and Patchstack and Cloudflare's CTO also describe early activity. CISA added both CVEs on 26 October per secondary coverage; its own page could not be opened for this refresh.

What they want

Not stated in public reporting. The early activity described is generic probing for exposed PHP servers.

What they did

Amazon Threat Intelligence reports targeting that began four days before the 21 October patches. CISA added CVE-2026-109618 and CVE-2026-109619 to its exploited list on 26 October, per press coverage. Public reporting describes exploit attempts against PHP servers and says working public exploits exist. One dissenting audit on Vulmon argues the use-after-free described for the second flaw does not exist in released PHP. Treat that point as contested until PHP or NVD settles it.

Who is at risk

Any PHP deployment reachable from the internet, including shared hosting, content management systems and custom applications. Patching the runtime is the fix. Filtering rules reduce exposure but do not close it.

What to do

  • Patch PHP to 8.5.12, 8.4.27, 8.3.36 or 8.2.35. On a managed host, get the runtime version confirmed in writing.
  • Hunt for requests to PHP endpoints from 20 October onward, and for unexpected child processes started by PHP-FPM or the web server user.
  • Check distribution packages against the PHP advisory's affected list, since some vendors backport fixes without changing the upstream version string.

Vulnerabilities

CVEs in this briefing
CVEProductCVSSCISA KEVFixed in
CVE-2026-109618PHP (core)9.2Not checked8.5.12, 8.4.27, 8.3.36, 8.2.35
CVE-2026-109619PHP (core)9.2Not checked8.5.12, 8.4.27, 8.3.36, 8.2.35

ATT&CK techniques

  • T1190: Exploit Public-Facing Application

Sectors: Cloud and hosting, Technology. Regions: Global.

Open next

Sources

Revision history

  • 2026-10-23: First published.
  • 2026-10-28: CISA added both CVEs to its exploited list on 26 October, per press coverage, with a federal deadline of 29 October. Amazon Threat Intelligence reports targeting began four days before the patches. The earlier line that CISA had not observed exploitation is withdrawn.

Newer: Sony So-net and plala member database accessed by a third party. Older: CVE-2026-110447: Nextcloud Collabora webshell attacks.