Today: Mon Nov 16, 2026MethodologyCorrectionsSource policyAboutResearch Desk
Home › Cyber Incidents and Threats › CISA adds two PHP remote code execution flaws to exploited...
Cyber Incidents and ThreatsQuiet

CISA adds two PHP remote code execution flaws to exploited list and sets federal patch deadline

On Oct. 21, 2026, the PHP project released fixes for two critical vulnerabilities that it said can allow unauthenticated remote code execution, and the US Cybersecurity and Infrastructure Security Agency urged organizations to patch immediately. On Oct. 26, CISA added both flaws to its Known Exploited Vulnerabilities Catalog, and security firm Rapid7 reported that CISA set an Oct. 29 remediation deadline for federal civilian agencies.[1][2][3][4]

Compiled by IPR5 sources22 attributed claimsUpdated Nov 6, 2026
Report a problem
Illustration, not a photo of this event.

The PHP releases

The PHP security team gave advance notice of a security release scheduled for Oct. 21 at 14:00 UTC, saying it addressed two critical vulnerabilities rated CVSS v4.0 9.2. PHP said versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35 fix the flaws, tracked as CVE-2026-109618 and CVE-2026-109619, and strongly encouraged all users to update immediately.[2][1]

PHP said it considers the risk highest for Apache mod_php, where a demonstrated exploit can be triggered by an unauthenticated request before any application code runs. It said there are no complete mitigations and that updating is the only safe choice.[2]

CISA's first alert

CISA's Oct. 21 alert strongly urged organizations to patch immediately. It said CISA had not observed exploitation as of the time of publication, and that organizations unable to update, or using PHP 8.1 or earlier, should take PHP-based systems offline until patched.[3]

Reports of exploitation attempts

Cloudflare CEO Matthew Prince wrote on X, as reported by ITPro, that Cloudflare saw thousands of attempts to exploit the flaw, rising to hundreds of thousands within two hours of the announcement and then to millions. Rapid7 said multiple public proof-of-concept exploits had become available and that, at the time of its update, it had not observed exploitation in the wild, though there were multiple reports of exploitation attempts.[5][1]

Known Exploited Vulnerabilities listing and deadline

The sources read do not establish which organizations, if any, were compromised or whether agencies met the deadline.[1]

Later PHP notices

PHP later suggested setting session.upload_progress.enabled=0 until its next regular bugfix release to guard against an unlikely remote code execution vector, CVE-2026-115560, which it said can only occur under an unusual combination of configuration and application code. It also announced rebuilt Windows packages including Brotli 1.2.1 to fix a separate Brotli vulnerability.[2]

The record

Event type
Official action or statement[4]Stated by Cybersecurity and Infrastructure Security Agency (CISA), official account, Oct 26, 2026
Means
Cyber[2]
Target type
Other[2]
Occurred, start
Oct 21, 2026[1]Stated by Rapid7, independent analysis, Oct 21, 2026
First reported
Oct 21, 2026The date of the earliest cited source
Primary place
United States (country)[4]Stated by Cybersecurity and Infrastructure Security Agency (CISA), official account, Oct 26, 2026
Next expected milestone
Federal civilian agency remediation due date[1]Stated by Rapid7, independent analysis, Oct 27, 2026
Next milestone date
Oct 29, 2026[1]Stated by Rapid7, independent analysis, Oct 27, 2026

Each value is what a cited source stated, with its source number. Where sources give different figures, the latest official account is listed first and every other figure is listed with it. A figure for one part of an event, such as one strike in a campaign, is listed as that part and never as the total.

Case and outcome record

DateStageWhoCourt, office or agencyAs the source states it
Oct 21, 2026IncidentPHP projectsecurity releases for two critical vulnerabilities[1]
Oct 26, 2026Official report or review releasedCybersecurity and Infrastructure Security Agency (CISA)added two vulnerabilities to the Known Exploited Vulnerabilities (KEV) Catalog[4]

One row per stage for each person, as sources report it. A stage a source only expects is not listed until it happens.

IPR records what each source says and who said it. A cited statement shows that a source said it, not that it is true. Hover a number to see the exact words quoted from that source. See something wrong? Use a flag to report it.

What the record does not show yet

  • What evidence of exploitation CISA relied on.
  • Whether any specific organization was compromised.
  • Whether federal agencies met the Oct. 29 deadline.