
Quick Answer
Agencies managing PHP websites can now check each client runtime against the fixed releases for CVE-2026-109618 and CVE-2026-109619, confirm package availability with the host, and document the deployed version. The vulnerabilities can enable unauthenticated remote code execution, and the PHP advisory says Apache with mod_php is particularly exposed.
What Happened
OpenAI reports that it coordinated a two-month response with PHP maintainers, researchers and security providers after agents and Wiz independently found and reported the vulnerabilities. PHP maintainers led the fixes and release, while partners including Wiz and Cloudflare contributed research, technical support and coordination.
On November 17, 2026, CloudLinux reported: “The release of the fixed PHP packages is complete. They are available in the stable repositories for CloudLinux OS 7, 8, 9, 10 and CloudLinux OS for Ubuntu 22.04.”
Are You Affected?
The vulnerabilities affect PHP installations that process web requests, including Apache with mod_php, PHP-FPM, php-cgi, FrankenPHP and LiteSpeed. The National Cyber Security Centre advises identifying PHP installations generally because all versions may be affected, rather than checking only outdated releases. Organizations using older PHP versions should move to a fully supported release.
The fixed releases are PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. The PHP project identifies Apache with mod_php as particularly at risk because a demonstrated exploit can trigger before application code runs. PHP 8.1 and older are no longer supported and do not receive standard security updates.
For the PHP-FPM deployment model, the PHP security advisory, updated November 3, 2026, states: “Source analysis indicates that FrankenPHP, analogous to Apache mod_php, calls the request shutdown procedure unconditionally, making it likely susceptible to application-independent attacks. LSAPI models FPM, with application-specific exploits being likely but unvalidated.” The same advisory says source analysis supports FPM as susceptible, although no complete FPM exploit has been demonstrated for that interface.
The Red Hat advisory says systems without PHP, or systems that do not expose PHP to untrusted HTTP requests, are not affected. It also states that PHP-FPM workers on Red Hat Enterprise Linux 8 and later exit on early initialization failures before reaching the corrupted structures, making remote code execution difficult in practice, while mod_php with its default configuration is at higher risk.
What to Do Now
- Ask the hosting provider or platform administrator to inventory every PHP installation and identify whether each site uses PHP-FPM, mod_php, php-cgi, FrankenPHP or LiteSpeed. Prioritize internet-facing systems.
- Apply the package containing the fixes for CVE-2026-109618 and CVE-2026-109619. The relevant fixed PHP releases are 8.5.12, 8.4.27, 8.3.36 and 8.2.35. CloudLinux clients can use a regular package update, then restart Apache, PHP-FPM or LiteSpeed as CloudLinux describes.
- Check the PHP package changelog for both CVE identifiers after the update, then verify that the fixed release is running rather than relying on the application version shown in the content management system.
- If a system cannot be updated immediately, follow the vendor mitigation guidance or consider taking it offline until it can be patched. Red Hat says configuration changes can block the vulnerable paths but may disrupt workloads and are not a substitute for patching.
- Review suspicious web requests, unexpected PHP worker behavior, unexplained process execution and unusual access to application files or databases before returning an affected service to production. The National Cyber Security Centre also recommends checking for backdoors where immediate updating or mitigation is not possible.
- Record the PHP version, package version, web server mode, update date, verification method and person responsible in the client record. This record should also identify any temporary protection and the planned permanent update.
What We’re Seeing
According to NewSunSEO, it read 59 WordPress sites in its managed hosting fleet on November 17, 2026. According to NewSunSEO, 58 of 59 sites run PHP 8.3.36, and the PHP version on one site was not readable. According to NewSunSEO, all 59 run WordPress 7.1.4.
Those figures apply only to NewSunSEO’s fleet. Delft Threat Intelligence Lab at Delft University of Technology reported “89,574 exploitation requests from 802 source IPs in 337 autonomous systems and 74 countries, 2026-10-21 08:37:17 to 2026-11-17 17:45:22 UTC.” Its data also records 182 source IP addresses that sent code or a dropper.
Why Agencies Should Check More Than the Application Version
The National Cyber Security Centre notes that PHP is used inside other products, so an agency may need to assess exposure across hosting layers and bundled software rather than at the WordPress dashboard alone.
That distinction affects the client record. An update can address the runtime vulnerability, but an agency also needs evidence that the fixed package is running and a record of the investigation performed on the affected service.
How Risk-Based Prioritization Applies to Client Websites
CISA’s Binding Operational Directive 26-04 defines four variables for federal agencies: asset exposure, KEV status, exploit automation and technical impact. Public exposure means that an unauthenticated or untrusted party can reach the asset over a public network. Partial control includes limited control over the behavior of the software that contains the vulnerability or information exposure about its behavior, while total control includes total control over the behavior of the software, including if the exploit reliably reveals log-in credentials.
The directive supersedes BOD 19-02 and BOD 22-01 and focuses remediation on higher-risk systems. For agencies, this provides a practical order for client conversations: identify internet-facing PHP systems, establish whether the vulnerabilities have known exploitation, determine whether exploitation can be automated and assess the access an attacker would gain.
Keep Temporary Protections in the Client Record
When a client cannot receive a fixed package immediately, the record should identify the temporary protection, its scope, the person who approved it and the permanent update path. A web application firewall rule or an offline service can occupy that entry until the runtime is patched and verified.
The Red Hat advisory states that patching is the only comprehensive solution that both fixes the vulnerabilities and preserves full functionality. It also says disabling session upload progress fully protects against CVE-2026-115560 and removes exposure to CVE-2026-109619 on the PHP package shipped with Red Hat Enterprise Linux 7, while other products receive protection only for confirmed session paths.
Key Considerations
- PHP 8.1 and older are unsupported and do not receive standard security updates, so clients on those releases need a supported upgrade or a vendor-provided backport.
- Configuration changes can reduce exposure but may disrupt workloads, and Red Hat says they are not a substitute for patching.
- Systems that do not expose PHP to untrusted HTTP requests are not affected by the flaws described in the Red Hat advisory.
- FrankenPHP is considered likely susceptible to application-independent attacks, while application-specific exploits against LSAPI are described as likely but unvalidated.
- A PHP runtime update does not replace checking the affected service for evidence of compromise.
FAQ
Which PHP Vulnerabilities Require Immediate Attention?
CVE-2026-109618 and CVE-2026-109619 are the two PHP request-handling vulnerabilities addressed by the fixed releases, and they can allow unauthenticated remote code execution.
Which PHP Versions Contain the Fixes?
The fixed releases are PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP 8.1 and older are no longer supported and do not receive standard security updates.
Which Hosting Configurations Need Priority?
Internet-facing PHP systems should be prioritized. Apache with mod_php is particularly at risk because a demonstrated exploit can trigger before application code runs. Affected configurations include PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed.
What Should a Website Agency Check First?
Inventory PHP installations with the hosting provider or platform administrator, identify the web server mode, and apply the appropriate fixed package. Then verify the running version, investigate the affected service for signs of compromise, and record the remediation details in the client record.
What Should Happen When an Update Cannot Be Applied Immediately?
Follow the relevant vendor mitigation guidance or consider taking the system offline until it can be updated. Red Hat says configuration changes can block the vulnerable paths but may disrupt workloads and are not a substitute for patching.
Related Coverage
- PHP security release fixes CVE-2026-109618 and CVE-2026-109619: PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 (October 21, 2026): PHP released four security builds on October 21, 2026 that fix two critical unauthenticated remote code execution flaws.
Sources
Do you want help with your SEO or website development? Then Contact Us Here.
NewSunSEO
Grow in Google and AI Search
AI-SEO, local search, paid ads and websites from one team, with offices on Long Island and in Myrtle Beach.
- AI-SEO
- Local AI-SEO
- AI Consulting
- PPC
- Web Design
- Web Development
- Long Island Office(631) 320-1700
- Myrtle Beach Office(843) 492-7131
Request a Free Proposal
Tell us about your business and where you want to grow.
We will reply by email to talk through your goals and what a proposal would include.