English edition · cyberattaques.org in FrenchFrançais
VulnerabilityExploited

CISA warns of exploited PHP flaw allowing unauthenticated remote code execution

On 26 October 2026 CISA added CVE-2026-109619, a PHP flaw that enables unauthenticated remote code execution, to its catalogue of actively exploited vulnerabilities. Any organisation running PHP servers or products that embed PHP is concerned.

What to do now Illustration photo (network cables)
CVSS severity9.2Critical
EPSS probability100 %
ExploitationConfirmed (CISA KEV)
PatchNone
Product
PHP (PHP Group)
Affected versions
Versions not specified in the source
Fixed in
Not specified in the source; refer to vendor guidance on php.net
CVE
CVE-2026-109619

The US Cybersecurity and Infrastructure Security Agency (CISA) listed CVE-2026-109619 in its Known Exploited Vulnerabilities catalogue on 26 October 2026, meaning it has evidence the flaw is being used in real attacks. The issue affects PHP, the language maintained by the PHP Group, and stems from internal request state that becomes stale and is carried over incorrectly.

According to the published description, a remote attacker can exploit the flaw without credentials to run code on the target system. The weakness classes attached to it include use-after-free, access of an uninitialised pointer and improper handling of exceptional conditions. CISA notes that the bug sits in an open-source component that many third-party products may ship, so exposure is not limited to PHP installations an administrator manages directly.

The source does not list affected or fixed PHP versions. It points to vendor guidance on php.net and to a CISA alert dated 21 October 2026 whose title states that critical PHP vulnerabilities require immediate patching. Whether the flaw has been used in ransomware campaigns is currently unknown.

US federal agencies bound by Binding Operational Directive 26-04 must act by 29 October 2026, only three days after the listing. CISA also requires forensic triage, indicating it believes systems may have been compromised before patching, and tells agencies to stop using the product if no mitigation is available. Organisations outside that scope can read the short deadline as a clear signal of how urgently to treat this flaw.

Action plan

What to do now

  1. Inventory every server and product running PHP today, starting with internet-facing systems.
  2. Apply the fixes or mitigations published by the PHP Group on php.net, along with updates from vendors whose products bundle PHP.
  3. Check exposed systems for signs of compromise such as unexpected processes, recently modified web files or unusual outbound connections, in line with CISA's forensic triage requirement.
  4. Where no mitigation is available for an exposed system, take it off the internet or out of service until a fix is applied.

Sources