HYPERNOVELTYINSTITUTE

Technical intelligence
for accelerating change.

Search the record

Home/Analysis

Daily Hypernovelty Lead · Cybersecurity & infrastructure · October 22, 2026

AI Found Critical Flaws in PHP. The Hard Part Is Getting the Web Patched.

AI helped researchers uncover two critical flaws in PHP. Emergency fixes are available, but protection still depends on hosts and operators getting them into the systems that actually run the web.

A systems engineer works through a server rack while warm maintenance light reaches only part of a larger data center

The patch exists. Protection arrives only when the running system has actually changed.

On October 21, 2026, the PHP project released emergency fixes for two critical vulnerabilities in software that runs websites across the internet. Researchers say AI helped uncover flaws that had survived for more than a decade. Maintainers and security partners had time to prepare before disclosure, but each affected operator still has to get the fix into use. A coordinated release gives defenders a head start; it cannot by itself protect an unpatched server.

The PHP project's security advisory confirms fixed versions: PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35, covering two vulnerabilities that can allow unauthenticated remote code execution. CVE-2026-109618 involves out-of-memory handling that interrupts partially initialized request data, causing cleanup routines to treat invalid data as valid. CVE-2026-109619 involves request-owned state that can survive after its backing memory is freed, leaving a later request handled by the same worker to act on stale data. Together they reach a CVSS severity score of 9.2, according to Wiz. CISA issued an independent alert the same day, urging immediate patching and prioritizing internet-facing systems.

Both vulnerabilities sit in the PHP runtime, not in application code. That distinction determines how exposure concentrates. Updating an application alone does not fix the underlying runtime risk. The PHP project notes that mod_php carries the highest demonstrated risk, with a confirmed unauthenticated exploit path that executes before the application itself runs. PHP-FPM, php-cgi, FrankenPHP, and LiteSpeed are also affected. The PHP project is unambiguous: only updating PHP is a complete solution.

How AI entered the picture

Wiz researchers Sagi Tzadik, Shir Tamari, Nir Ohfeld, and Tomer Schwartz report that affected releases extend back to PHP 5.4, with at least one issue affecting nearly every version in that historical range before the fixes. They describe flaws hidden for more than a decade. They also report that AI substantially reduced the barriers to establishing exploitability across what they describe as exceptionally complex vulnerability chains, and that the flaws could enable not only remote code execution but process memory disclosure, potentially exposing credentials, tokens, API keys, and certificates.

OpenAI reports that Calif independently identified a critical flaw using GPT-5.6 Sol as part of its Patch the Planet initiative. The coalition worked over roughly the past two months, with PHP maintainers leading the development and release of fixes while partners contributed research, technical support, and coordination and prepared protective mitigations before disclosure.

These are accounts from participants with an interest in demonstrating their tools' capabilities, rather than independent timing benchmarks. Wiz describes AI reducing the difficulty of establishing exploitability; OpenAI identifies an AI-assisted independent discovery. They support a concrete conclusion: researchers are using these tools to investigate old code and produce findings that require a coordinated operational response. They do not tell us exactly how much faster the same work would have been than a comparable human-only investigation.

The defender's window

OpenAI describes the advance coordination period as a "Defender's Window," stating that to their knowledge frontier AI found these vulnerabilities before attackers did. CISA's October 21 alert says the agency had not observed exploitation as of the time of publication. That statement is time-bounded: Patchstack, a WordPress security vendor, published a same-day timeline saying hosting partners had reported multiple exploitation incidents, while a later update said Patchstack's own telemetry showed probing but no hard evidence of breaches. The vendor reports do not establish mass compromise, and they do not contradict CISA's narrower account of what the agency had observed when it published its alert.

OpenAI also warns explicitly that the same AI capabilities that aided discovery can help attackers develop working exploits now that vulnerability details are public.

The PHP project confirms that Linux distribution and LTS vendors received patches in advance. That gave providers preparation time. Once the details are public, defenders have to assume attackers can study them too.

Verification bottleneck

Patch availability and deployed protection are not the same thing. That gap is where residual risk concentrates after a disclosure of this kind.

PHP can sit inside packaged applications and platforms where its presence is not obvious to the operator. A site operator whose PHP environment is managed by a hosting provider depends on that provider to push the update to the actual running environment. Confirming protection requires checking the running software against the provider's security advisory, including any backported fix. A scheduled update is insufficient evidence. CISA's guidance notes explicitly that PHP may be embedded in other software and that its presence within an organization may not be directly visible.

Version distribution adds another layer. The PHP project has issued patches across its four currently supported branches. PHP 8.1 and older are outside the project's support scope. Some Linux distribution and LTS vendors provide backports for older versions, and the PHP project has supplied minimal source-backport patches for 7.4, 8.0, and 8.1 as a reference. Organizations on those versions depend on vendor packages or face a more substantial upgrade decision under time pressure.

An organization still needs someone who knows which systems it runs, who can authorize a change, and how to confirm that an update applied without breaking the service. AI's contribution to this research does not demonstrate that it can remove that coordination work. If discovery accelerates faster than deployment capacity, organizations could face more urgent findings than they can safely resolve. That is a risk to prepare for, rather than a measured result of this incident.

WAF and hosting-layer mitigations can reduce specific attack paths in the interim. The PHP project states directly that they do not make an installation safe; CISA treats them as a temporary supplement pending patching, not a replacement for it.

What to do

The immediate step is inventory: locate every PHP installation, including those embedded in packaged or managed software, determine the running version, and confirm what updates are available from your vendor or package manager. CISA advises organizations that cannot update immediately, or that continue to use PHP 8.1 or earlier unsupported versions, to take PHP-based systems offline until they can be patched or updated.

This response shows how AI-assisted research can give maintainers time to act. Preserving that advantage across repeated discoveries will require investment in the people and processes that carry fixes into running systems. For a website owner, that becomes a practical accountability question: who maintains the underlying software, and what evidence can they provide that the security update is actually in place? Without a clear answer, a successful discovery and a published patch still leave the owner waiting for protection.


Operator note: versions, backports, and CISA guidance

Fixed versions are PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35. If PHP is managed through a Linux distribution or LTS vendor package manager, check for vendor-issued security packages before compiling from source. PHP 8.1 and earlier are not supported by the PHP project; vendor backports exist for some distributions, and the PHP project has published minimal source backports for 7.4, 8.0, and 8.1 as a reference. CISA advises taking PHP-based systems offline if they cannot be updated immediately or continue to run PHP 8.1 or earlier unsupported versions, until they can be patched or updated. WAF coverage may reduce specific attack paths in the interim but is not a substitute for patching. Review the CISA alert and the PHP project advisory for guidance applicable to your environment.

Back to the archive