Skip to content
NewA calmer, faster ZeroHour
Exploit / PoCcriticalExploited in the wild

PHP2Shell flaws were exploited within days; CISA set a federal deadline

Original title: How exposure management can help public sector prepare for PHP2Shell-like vulnerabilities

Tenable Blogby Kate Boronkay ()11 min read2
Part of a story covered by 4 sourcesPHP2Shell flaws patched after leak and confirmed exploitationMerged summary & timeline
AI summary · x-ai/grok-4.7Summaries by Vani AI

Fixes are PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35; Nov. 19 builds also fix CVE-2026-115560.

Tenable recounts how two critical PHP runtime flaws, CVE-2026-109618 and CVE-2026-109619, leaked before an Oct. 20 disclosure and were patched a day early on Oct. 21. CISA confirmed active exploitation, added them to KEV on Oct. 26, and gave federal civilian agencies until Oct. 29 under BOD 26-04. Agencies including NSA, FBI, NCSC, CERT-EU, and ACSC urged patching or taking systems offline. Researchers report chaining with the Linux kernel flaw Fragnesia, while a separate critical PHP flaw fixed Nov. 19 had no reported exploitation at release.

Unconfirmed: The 25-server root-access figure is Dream Research's report, which Unit 42 says it independently verified.

Key facts
  • About 30.3 million PHP services were on affected versions as of Oct. 29, Tenable says, citing scanning.
  • Nov. 19 fixed builds are PHP 8.5.13, 8.4.28, 8.3.37, and 8.2.36.
  • CISA added Fragnesia, CVE-2026-46300, to KEV on Oct. 28.
  • Dream Research says chaining reached root on 25 servers; Unit 42 says it verified the tooling.
  • CVE-2026-115560 depends on session configuration and libraries and had no reported exploitation.
Security assessment · AI, from the articleExploited in the wild

Impact: Unauthenticated remote code execution on PHP web servers

ProductAffectedFixed in
PHPaffected versions before the emergency PHP2Shell fixes8.5.12, 8.4.27, 8.3.36, 8.2.35; also 8.5.13, 8.4.28, 8.3.37, 8.2.36
What to do
  1. 1.Upgrade to the Nov. 19 PHP releases, or take affected systems offline.
  2. 2.Patch kernels and restrict unprivileged user namespaces to limit post-exploit escalation.
  3. 3.Prioritize using KEV status, exploit evidence, and internet exposure, not severity alone.
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

Vulnerabilities mentioned

All
CVEVulnerabilityCVSSEPSSSignalsPublished
CVE-2026-109618
+1 related CVE
OOM longjmp memory flaw enabling RCE in PHP
9.2100%KEVPoC ×25
KEV
CVE-2026-115560
Session serializer mismatch RCE in PHP
9.271%PoC ×11
CVE-2026-46300
Shared-frag marker loss in Linux kernel skb coalescing (LPE)
7.817%KEVPoC
KEV

From the original article

11 min read at tenable.com

PHP2Shell showed how fast a runtime-level flaw can go from disclosure to confirmed exploitation. Here’s how federal, state, local, and education teams can prepare for PHP2Shell-like flaws. Key takeaways PHP2Shell went from disclosure to confirmed exploitation within days.

Tenable Blog

By Kate Boronkay · tenable.com

Read the full article at Tenable Blog

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.