The PHP project released security updates for four release branches on October 21, 2026, after researchers discovered two critical vulnerabilities affecting PHP versions back to 2004. The NSA reportedly advised taking unpatched websites offline until they can be updated.
PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 contain the fixes. OpenAI and Wiz used AI-assisted research to find the flaws, which reportedly allow remote code execution and could affect 70 percent of internet deployments. No known exploitation existed at disclosure, but operators should prioritize patching their server runtime separately from any WordPress updates.
The PHP project released security updates for four release branches on October 21, 2026, giving website operators an immediate patching path after researchers uncovered two critical vulnerabilities. The PHP Foundation’s announcement listing names PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35.
The NSA’s guidance is unusually strong: websites that cannot be patched immediately should be taken offline until they can be fixed, TechCrunch reports. The same report says the flaws reach back to PHP 5, released in 2004, and that OpenAI reported no known exploitation in the wild at disclosure. That is a time-bound observation, not a reason to postpone updating.
The immediate job is to patch the PHP runtime serving the website. Updating WordPress or another content management system alone is a separate task. The discovery also offers a useful example of AI-assisted security research: models helped researchers find the problems, while coordinated work with maintainers produced fixes before public disclosure.
Four PHP Branches Have Published Security Updates
The Foundation’s October 21 listing matters because it identifies more remediation options than a single recommendation to install the newest PHP release.
TechCrunch recommends PHP 8.5.12, describing it as the current release. The Foundation’s list shows that operators already using another listed branch also have a branch-specific security release to evaluate.
That distinction has practical value. For a team running PHP 8.4, I’d start by assessing the published 8.4.27 update instead of assuming that emergency remediation requires a move to PHP 8.5. A security update and a broader version migration can involve different compatibility checks. The Foundation’s list supports treating those as separate decisions.
Work with Zeniteq
Promote your app with us
Reach readers exploring AI tools and workflows. Discover sponsorship and advertising options for your app.
Older installations face a more substantial maintenance problem. TechCrunch reports that PHP 8.1 and earlier are no longer supported, so administrators on those versions should plan an upgrade to a supported branch.
The Foundation page available here is an announcement summary, not the full security advisory. It does not supply CVE identifiers, exact vulnerable version ranges, root causes or exploitation prerequisites. The NSA guidance and detailed discovery account below come through TechCrunch’s reporting. Those limits prevent a configuration-by-configuration exposure assessment, but they do not change the published patch options.
This Is a Server Runtime Issue, Including for WordPress
PHP runs application code on the server. A WordPress installation uses that runtime, but WordPress files and the PHP interpreter are different software components with potentially different update owners.
A CMS update changes the application. A PHP update changes the software executing it. Completing one job therefore gives no assurance that the other has happened.
According to TechCrunch, WordPress explicitly said the vulnerabilities are not WordPress-specific and advised site owners to patch their servers and work with their hosting providers. The practical consequence is straightforward: a website owner may need the host to change the deployed PHP version, even when the owner can update WordPress independently.
TechCrunch reports that the flaws could allow attackers to access a server’s file system or an application’s database. Wiz’s homepage promotes the findings under the name PHP2Shell and describes them as critical remote code execution vulnerabilities. Remote code execution means an attacker can cause code to run on a remote system; the resulting access depends on the process’s permissions and surrounding controls.
Wiz also describes the vulnerabilities as affecting 70% of the internet. That is vendor framing, not a measured count of exploitable websites. PHP’s widespread deployment explains the potential scale, but language usage alone cannot establish whether every installation meets an exploit’s conditions.
I’d prioritize an accurate runtime inventory over a headline-sized estimate of affected sites. An operator needs to know which PHP versions actually serve their applications, who controls those deployments and whether the security update has reached them.
OpenAI and Wiz Used AI in Separate Research Efforts
The discoveries involved distinct research efforts that converged on coordinated remediation.
According to TechCrunch’s October 21 report, security testing company Calif participated in OpenAI’s Patch the Planet initiative and used GPT-5.6 Sol to find one of the vulnerabilities.
Separately, Wiz used its Wiz Atlas security agent alongside Gemini 4 Argon and GPT-5.6 Sol to discover multiple PHP vulnerabilities. The available account identifies the tools involved, but provides no model-by-model measurements showing which system contributed most or how much researcher time it saved.
The consequential part is what followed discovery. TechCrunch reports that both groups worked with PHP on patches before publicly disclosing the flaws. Researchers then collaborated to develop the findings further and test the fixes. Wiz credited assistance from organizations including Automattic, Akamai, AWS, Cloudflare, Fastly, Imperva, Microsoft and Vercel.
This is a stronger basis for evaluating the work than the model names alone. Finding a suspected bug creates a research lead. Coordinating with maintainers, validating the issue and testing a patch turns that lead into something operators can act on.
The published account supports describing this as AI-assisted research within a coordinated security process. It provides no basis for claiming that a model independently secured PHP or that one AI system outperformed another.
AI Can Also Reduce the Work Needed to Adapt Exploits
Wiz’s warning concerns the work required to make an exploit function across different deployments. As quoted by TechCrunch:
“LLMs can help adapt an exploit to different PHP versions, configurations and memory layouts”
An exploit that works against one environment may require changes to work against another. PHP versions, server configuration and memory layout can all matter. Wiz’s argument is that language models can help with that adaptation work, potentially lowering an attacker’s effort.
That is a vendor assessment of risk, not evidence that attackers had already weaponized these particular flaws. OpenAI’s reported absence of known exploitation at disclosure remains the relevant observation about activity at that moment.
The two points can coexist. Researchers can discover a vulnerability before known attacks, while public disclosure creates a new window in which attackers examine the issue and operators deploy fixes.
My view is that the defensible lesson is about timing: AI-assisted discovery is most useful when maintainers receive findings early enough to prepare remediation. Here, the reported coordination gave administrators published releases to install when the news became public.
Verify the Deployed Runtime, Not Only the Update Request
A published patch and a patched website are different states. Operators should close that gap with a short, deployment-focused check:
Identify the active PHP branch. Confirm the runtime serving each relevant application, rather than relying solely on a CMS dashboard or an old hosting record.
Assign the update to the right owner. On managed hosting, ask the provider which security release is deployed. On self-managed infrastructure, the server or platform team needs to handle the runtime update.
Use the published release for the appropriate branch. The Foundation lists fixes for PHP 8.2, 8.3, 8.4 and 8.5.
Confirm the version after deployment. An approved change request or downloaded package is not confirmation that the website is running the updated runtime.
Check the application after updating. Verify that essential site functions still work, particularly when remediation requires moving off an unsupported PHP branch.
If immediate patching is impossible, the reported NSA guidance is to take the site offline until it can be fixed. That is a disruptive option, especially for revenue-generating services, but the recommendation should be weighed against the reported severity and the exposure of the unpatched runtime.
Frequently Asked Questions
3 questions
1
Which PHP Releases Contain the Published Fixes?
The PHP Foundation lists 8.5.12, 8.4.27, 8.3.36 and 8.2.35 in its October 21, 2026 security-release announcement.
2
Will Updating WordPress Fix the PHP Vulnerabilities?
A WordPress update alone does not confirm PHP remediation. The server’s PHP runtime must also be updated, potentially by the hosting provider.
3
Were Attackers Exploiting the Flaws at Disclosure?
According to TechCrunch, OpenAI reported no known exploitation in the wild at disclosure. That observation can change and should not delay patching.
