CybersecurityIn the news

PHP2Shell and KEV Forensic Triage: Evidence First, Then the Patch

Yahia Aboushadi
Director of Brand and Marketing, Pyramid Systems
Reading time:
6 min.

On October 26, 2026, the Cybersecurity and Infrastructure Security Agency (CISA) added the two PHP flaws known as PHP2Shell to its Known Exploited Vulnerabilities (KEV) catalog, with an October 29 due date. Both entries are flagged for forensic triage. If your team treated this as a patching job, check whether evidence survived the patch and whether the fix reached every copy of PHP.

What does the PHP2Shell KEV entry require?

Mitigate the flaw and assess whether the system was compromised. The entries for CVE-2026-109618 and CVE-2026-109619 tell agencies to apply vendor mitigations under Binding Operational Directive (BOD) 26-04 and its "Forensics Triage Requirements," or stop using the product if mitigations are unavailable. Both set forensicTriage to "Yes." According to Covington's summary, the BOD says that means the agency must also "carry out a forensic triage of the asset to assess whether the system is compromised." Our KEV explainer covers how these fields work.

One date needs care. FedRAMP's notice NTC-0014 says agencies must begin evaluating and remediating on BOD 26-04 timelines by December 7, 2026, while the catalog already lists BOD 26-04 due dates. The timeline for an asset also turns on its exposure, which each agency evaluates. The sources we reviewed don't settle how those fit together for this listing, so ask your CISO's office rather than assuming one date covers every asset.

In what order should triage and patching happen?

Evidence first. The BOD's implementation guidance recommends a sequence counted from the KEV listing. These are recommended practices, as Covington summarizes them; the triage itself is the requirement. We worked from that summary, so check the guidance before you encode the hours in a runbook.

Hours after KEV listing Recommended step
Within 2 Decide whether the listing requires triage; activate the response team; set up out-of-band communications
2 to 24 Preserve volatile data, collect evidence, then apply critical patches
6 to 24 Begin containment, without destroying evidence or alerting the actor
24 to 48 Analyze evidence for unauthorized access, lateral movement, persistence and data staging or exfiltration
48 to 72 Produce a forensic triage report with timelines, findings and next steps

For PHP2Shell, the analysis window starts earlier than the listing. Datadog Security Labs says AWS reported exploitation attempts as early as October 17, four days before PHP shipped its fixes on October 21. We'd treat that as the latest reasonable start for a lookback, not a proven first date, and preserve those logs before rotation removes them.

Datadog suggests looking for memory-exhaustion errors during request initialization and unexpected shell processes, along with large form submissions, though it warns that body size alone is a weak signal. CISA's alert, as ITPro reports it, adds PHP worker processes launching shells or downloading tools. A quiet crash log proves little, since Datadog notes that successful command execution doesn't necessarily crash the worker.

Include CVE-2026-46300 in the same review. CISA added this Linux kernel flaw on October 28, due October 31 with triage flagged, and says it "can be chained with" the PHP flaws "to implant PHP webshells and run commands as root."

Where can PHP hide from a patch report?

Inside other products. CISA's alert, as ITPro reports it, warns that PHP's prevalence "may not be directly observable," and a former Department of Homeland Security CISO told Federal News Network that vulnerable components may sit where traditional scanning doesn't immediately find them.

Where Why it gets missed What to check
Network appliances Palo Alto Networks lists PAN-OS and Panorama management interfaces as affected, with fixes such as PAN-OS 11.1.16-h4 The vendor's version matrix; management access limited to trusted internal addresses
Linux distribution packages Ubuntu's fixed PHP 8.3 is 8.3.6-0ubuntu0.24.04.13, well below the upstream 8.3.36 number The distribution's CVE page, not the upstream version
Containers and bundled apps They carry their own interpreter Rebuild and redeploy the image, then check what is running
Command line vs. web runtime Datadog warns the command-line PHP can differ from the one serving requests The version the web runtime reports
Long-running workers An updated package doesn't replace a process already running Restart or replace every worker

PHP 8.1 and older need their own decision. The PHP project no longer updates those branches beyond minimal source backports for 7.4, 8.0 and 8.1. CISA's alert, as ITPro reports it, says organizations on those versions or unable to update "should take PHP-based systems offline until they can be patched or updated."

Does configuration change the risk?

It changes how hard exploitation is, and it doesn't remove a system from scope. PHP rates the risk highest for Apache with mod_php and lists PHP-FPM, php-cgi, FrankenPHP and LiteSpeed as affected. For CVE-2026-109618, Red Hat assigns a rating of Important and a CVSS v3 score of 8.1 against the National Vulnerability Database's 9.8, saying remote code execution is "difficult in practice" on standard Red Hat Enterprise Linux deployments using PHP-FPM. That language applies to that CVE only. Datadog says PHP confirmed command execution on both mod_php and PHP-FPM for an upload path of CVE-2026-109619, with PHP-FPM also needing a suitable operation from the application.

Exploitation itself is confirmed. CISA listed both flaws, and Palo Alto Networks says active exploitation "has been observed" against management interfaces exposed to the internet. How many production systems were compromised is not known: The Register reports CISA hasn't disclosed that, that some early claims were withdrawn, and that one researcher's successful honeypot runs used a "favorable single-worker configuration."

What about CVE-2026-115560?

It is a separate PHP issue, and the October 21 releases don't fix it. PHP calls the required setup "unlikely in practice," because an application must switch its session serialize handler at runtime with upload progress still enabled. PHP suggests setting session.upload_progress.enabled=0 until its next regular release, and says applications that never change the handler at runtime can keep the feature on. It wasn't in the KEV catalog as of the October 30 feed.

How does this reach contractors?

Through the contract, if at all. Covington reports that BOD 26-04 covers systems another entity operates on an agency's behalf, says it doesn't apply directly to contractors unless the governing contract requires it, and directs agencies to review their contracts. Your contracting officer decides what that means for your system. FedRAMP's December 7 rules are a parallel track, described in our KEV explainer.

Closing out a PHP2Shell listing

  1. Search for PHP across appliances, images and vendor products, and record each asset's owner and exposure.
  2. Verify each fix against that vendor's advisory, restart workers and recheck the running service.
  3. Preserve logs from October 17 forward. If a system is still unpatched, collect volatile evidence first.
  4. Write the triage up, including any evidence lost to an earlier patch or restart.
  5. Set a date for PHP 8.1 and older, and for 8.2, which PHP says reaches end of life on December 31, 2026.

The Bottom Line

For PHP2Shell, patching and triage share one window, and evidence comes first in CISA's recommended order. If you patched without collecting evidence, record that, run the analysis with what you still have, and confirm the fix reached every copy of PHP. Our cybersecurity teams support federal programs on FISMA and NIST compliance.

FAQ

What is PHP2Shell?

It is the common name for CVE-2026-109618 and CVE-2026-109619, two critical flaws in the PHP engine that can allow unauthenticated remote code execution. PHP fixed them on October 21, 2026 in versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35.

Was the PHP2Shell deadline binding on contractors?

BOD 26-04 is directed to federal agencies and, per Covington's summary, says it does not apply directly to contractors unless the governing contract requires it. It also tells agencies to review their contracts. Ask your contracting officer how it applies to a system you operate for an agency.

Does session.upload_progress.enabled=0 fix PHP2Shell?

No. PHP lists it as a measure that blocks the confirmed session paths for CVE-2026-109619, not other variants, and says updating is the only safe choice. It is also PHP's advice for the separate CVE-2026-115560 until the next regular release.

Are PHP-FPM servers safe from PHP2Shell?

Don't assume so. PHP lists PHP-FPM among the affected deployments while rating the risk highest for mod_php. Red Hat's record for CVE-2026-109618 says remote code execution is difficult in practice on standard Red Hat Enterprise Linux deployments using PHP-FPM, but Datadog says PHP confirmed command execution on both mod_php and PHP-FPM for an upload path of CVE-2026-109619, with PHP-FPM also needing a suitable operation from the application.

Sources

  1. CISA, Known Exploited Vulnerabilities Catalog, JSON data feed (released October 30, 2026)
  2. PHP Group, News Archive 2026, security advisories of October 21 and 23 and Windows builds of October 26
  3. Palo Alto Networks, Impact of Critical Vulnerabilities in PHP on Palo Alto Networks Products (updated October 29, 2026)
  4. Ubuntu Security, CVE-2026-109618
  5. Red Hat, CVE-2026-109618
  6. Datadog Security Labs, PHP2Shell, detection, analysis and remediation (updated October 23, 2026)
  7. Covington Inside Privacy, CISA Releases Binding Operational Directive on Prioritizing Security Updates Based on Risk (June 17, 2026)
  8. FedRAMP, NTC-0014, FedRAMP Response to CISA BOD 26-04 (June 16, 2026)

How we researched this. Every number, date and requirement here is checked against the sources listed above, primary documents first, and the post is fact-checked again before publication. When a rule, date or status changes, we update the post and log the change below. Read our editorial standards or send a correction.

Yahia Aboushadi
About the author. Yahia Aboushadi is Director of Brand and Marketing at Pyramid Systems, an employee-owned federal IT firm in Fairfax, Virginia, that has delivered for federal agencies since 1995. . Connect on LinkedIn.

Continue reading

Related Insights

More from Pyramid Systems on federal cybersecurity.

An empty meeting room with a long wooden table, pink chairs and a wall screen

Cybersecurity

22 November 2026
How to Run a Ransomware Tabletop Exercise That Tests Federal Reporting Rules

How to plan a ransomware tabletop exercise for a federal system: CISA's planning timeline, roles, injects tied to NIST and DFARS rules, and the after-action plan.

Read more
Rows of server cooling fans lit in purple and blue in a data center, the kind of hardware managed by vCenter servers exposed to CVE-2026-123890

Cybersecurity

21 November 2026
VMSA-2026-0009 and CVE-2026-123890: What a Patched vCenter Still Doesn't Fix

CVE-2026-123890 lets an attacker with network access bypass vCenter authentication. The fixed builds, the KEV entry and what to check on vCenter and ESX hosts.

Read more
A data center floor with server cabinets under overhead cable trays, illustrating a post on the GAO zero trust report

Zero Trust & Identity

20 November 2026
The GAO Zero Trust Report's 40 Recommendations, Sorted by What Agency Plans Lack

The GAO zero trust report found 17 of 22 civilian agency plans did not fully address federal guidance. What its 40 recommendations ask for and how to check yours.

Read more
Front of a rack server with rows of drive bays and green status lights, the kind of x86 host where Java4Shell exposure gets checked

Cybersecurity

18 November 2026
Java4Shell (CVE-2026-114938): Which Java Hosts Are Exposed and What to Patch First

Java4Shell needs three things to line up: an affected JDK line, an AVX-512 VBMI processor and attacker-supplied Base64. How to find exposed hosts and patch first.

Read more