Technology & security · · Updated · 11 min read · By Alexander
Critical PHP vulnerabilities: What you should clarify with your hosting provider now
The PHP security updates of 19 November 2026 fix critical vulnerabilities, including independent new flaws. Ask your hosting provider to update the PHP runtime actually used by your website and confirm the active fixes. Update and clarification of 20 November 2026: We have added information about Cloudflare’s filter for web requests (web application firewall, or WAF) and its limitations. The documented rules can provide additional protection; the PHP update remains necessary. Research status: 20 November 2026, around 22:00 CET.

What happened?
The release package contains 18 CVE fixes: 17 PHP CNA advisories, meaning official security notices from the PHP project, plus the library fix for uriparser (CVE-2026-48841). Under CVSS v4.0, seven PHP advisories are each rated 9,2 and “critical”. CVE identifiers refer to individual vulnerabilities.
CVE-2026-115560 was already known from the October addendum to PHP2Shell. Other fixes address PHP2Shell issues that had not been fully resolved. Independent new flaws, particularly in request processing, make the November package a security event in its own right. The original PHP2Shell CVEs do not count as new November vulnerabilities. The seven critical flaws are:
- Session data: CVE-2026-115560 affects enabled upload progress and different storage formats, known as serializers, when writing to and reading from the same session store. A serializer change at runtime is not required: applications or pools with different fixed settings and shared storage may also be affected. CVE-2026-126714 concerns session files that are partially overwritten after an interrupted write of controllable data. With suitable call chains in the application, code execution is possible with both flaws.
- Request processing: under certain conditions, CVE-2026-129289 enables unauthenticated code execution in PHP-FPM, a PHP execution service: reused FastCGI connections and php://input opened by the application but not fully read. The described default nginx/Apache configurations close these connections. Processing disruptions and outages are described for the alternative LSAPI integration; equivalent code execution has not been demonstrated.
- Error handling and sessions: CVE-2026-129182 (PHP 8.5) and CVE-2026-129481 (PHP 8.3 to 8.5) allow access to freed memory in subsequent requests handled by the same worker process during certain error sequences. Crashes have been demonstrated; code execution through these paths has not been proven. For 129182, the described FPM path requires PHP_VALUE/PHP_ADMIN_VALUE settings passed by the frontend; ordinary pool or .user.ini settings alone are not sufficient. CVE-2026-129474 (PHP 8.5) concerns error diagnostics for certain method calls with fatal_error_backtraces=1 and zend.exception_ignore_args=0. The code-execution demonstration requires controllable request data and known memory addresses.
- Time zone cache: CVE-2026-129496 affects certain PHP build variants (NTS) during early startup diagnostics in combination with PHP file logging. Crashes have been demonstrated, while code execution has only been shown in local test setups with known memory addresses and further prerequisites. A complete remote attack that bypasses address space layout randomisation (ASLR) has not been demonstrated. FPM’s own log alone is not a sufficient prerequisite.
How dangerous is this in practice?
CVSS assesses technical severity, not the likelihood of exploitation. Whether a flaw can be reached on your website depends on the application and server configuration. A score of 9,2 therefore does not mean that every PHP page can be exploited immediately.
Public research such as “phpAfterShell” on CVE-2026-126714 and PoCs, meaning technical proofs of concept, demonstrate attack possibilities under certain conditions. As of the research date, the primary sources reviewed do not confirm successful active exploitation of the new November CVEs on production systems. An attempted attack does not prove a breach.
As of 20 November 2026 (18:48 CET), none of the seven critical CVEs listed above is included in the CISA KEV catalogue of known exploited vulnerabilities. Compared with the catalogue reviewed on 18 November, none of these seven had been added. Older PHP2Shell entries do not demonstrate exploitation of these seven flaws. The absence of an entry does not prove that exploitation is not taking place.
Update and clarification of 20 November: Cloudflare documents WAF rules for known phpAfterShell patterns and the session serializer flaw. The association with CVE-2026-115560 was already documented on 23 October; the November rules update is dated 19 November. The blog post of 20 November does not confirm active exploitation and provides no figures for attacks or blocks. A configured “Block” action and a research proof do not establish that your website was attacked or compromised.
Which PHP versions contain the fixes?
The PHP project confirms the following fixed versions for the respective branches. This is not an assurance against all security vulnerabilities.
- PHP 8.2: 8.2.36
- PHP 8.3: 8.3.37
- PHP 8.4: 8.4.28
- PHP 8.5: 8.5.13
- PHP 8.6: new stable version 8.6.0
There is no need to move to 8.6 if a corrective update is available in the existing supported branch. Shared session storage still requires matching serializer settings.
Plesk confirms backports for Linux for 8.1.34, 8.0.30 and 7.4.33: fixes with an unchanged base version number. Only matching the installed vendor package to the backport evidence demonstrates the fixed status. The notice reviewed does not provide evidence of corresponding Windows backports.
Plesk 18.0.82 Update 4 and 18.0.81 Update 9 update the panel components sw-engine/plesk-engine to PHP 8.4.28. For EasyApache 8.2 to 8.5, cPanel lists the fixed versions above; internally, for v110 it lists PHP 8.1.34, and for v134/v138 and WP Squared it lists PHP 8.4.28. The website and panel runtimes must be checked separately.
According to the status at 17:54 Central European Time, CloudLinux has released selected alt-php and ea-php packages, but not yet for all channels. For ea-php 7.4/8.0/8.1, “.cloudlinux.2” is part of the fixed release identifier. Ask for confirmation of the package actually in use.
How can I check my website’s PHP runtime?
WordPress shows the PHP version under “Tools → Site Health → Report/Info → Server”. In Plesk, go to “Websites & Domains → PHP Settings” for your domain. Make a note of the handler, meaning the PHP integration. A new version that is merely installed server-wide is not sufficient.
In cPanel, the “MultiPHP Manager” shows the selected or inherited version for each domain and, where applicable, the PHP-FPM assignment. The provider decides whether this interface is available. If you cannot see this information, ask directly for the package version used by your domain.
With SSH, “php -v” only shows the command-line runtime, known as CLI. The website may use a different version or configuration. Its Web-SAPI, the web server’s PHP integration, is what matters. After the update, check the web display again and ask for confirmation that the workers, meaning the worker processes, have been restarted or fully replaced.
What should I write to my hosting provider?
Copy this text and add your domain:
Hello, please confirm for [DOMAIN] the installed and active PHP fixes from the entire release package dated 19.11.2026, particularly CVE-2026-115560, CVE-2026-126714, CVE-2026-129182, CVE-2026-129289, CVE-2026-129474, CVE-2026-129481, CVE-2026-129496 and the FPM privilege escalation CVE-2026-129291. For each web handler, please state the full package/build identifier, including the vendor suffix, build date and security or backport evidence. Please also check any differing CLI/Cron runtimes and, where applicable, the panel runtime. When were all affected workers restarted or fully replaced? Which web runtime is active afterwards? Please state the scope and result of a review for signs of compromise; preserve relevant logs if there is any suspicion. If the update is still pending, I need a binding date and the CVE-specific measures that will be effective until then. Thank you.
What if the update cannot be installed immediately?
There is no documented universal workaround. These examples are for the hosting provider or administrator and do not replace the update.
- CVE-2026-115560: administratively disable upload progress if it is not needed by setting session.upload_progress.enabled=0. If it is required, the serializers for shared session storage must match. Changing this only in the application code is too late. The update changes the default; an explicit =1 remains relevant. For CVE-2026-126714, also limit untrusted session content; this remains incomplete protection as well.
- CVE-2026-129289: disable reuse of FastCGI connections between the web server and PHP. Request data that is normally read in full is not a reliable substitute because of possible error sequences. For CVE-2026-129481, the advisory temporarily recommends pm.max_requests=1 with FPM and a restart, at a performance cost; disabling upload progress or enabling OPcache is not reliably sufficient in this case.
- CVE-2026-129182: enforce fatal_error_backtraces=0 to prevent overwriting. For CVE-2026-129474, this setting or zend.exception_ignore_args=1 applies; display_errors=0 alone is not sufficient. Restart the workers afterwards. For CVE-2026-129496, eliminate triggering startup warnings or invalid/outdated configuration, consider an alternative logging route such as syslog, and restart the master/workers. Merely changing the configuration does not reliably clean up affected processes that are already running.
Cloudflare documents two PHP RCE rules for known phpAfterShell patterns (CVE-2026-126714) and the session serializer flaw (CVE-2026-115560): one in the “Free Managed Ruleset” and one in the “Cloudflare Managed Ruleset”. According to the vendor, both are set to “Block” by default. The “Free Managed Ruleset”, a ruleset maintained by Cloudflare, is available on all plans and deployed by default on the Free plan.
The “Cloudflare Managed Ruleset” is available on Pro, Business and Enterprise, but not on the Free plan. The ruleset must also actually be enabled for the website. Its PHP-FPM rule for CVE-2026-129289 is initially set to “Log”: it logs matching requests but does not block them. Ask your hosting provider to review the logged requests before changing the rule to “Block” if appropriate; legitimate requests can also trigger a rule.
For CVE-2026-129182, CVE-2026-129474, CVE-2026-129481 and CVE-2026-129496, the Cloudflare post reviewed does not specify a dedicated WAF rule. Complete protection against all vulnerabilities covered here has therefore not been demonstrated.
Your website’s web requests must actually pass through Cloudflare. Using Cloudflare only as a DNS service is not sufficient. Ask your hosting provider to check whether the appropriate rulesets are active and which actions or exceptions apply. They should also check whether unwanted direct access to the actual web server (origin) is blocked: such access can bypass the WAF. The rules filter web requests over HTTP and HTTPS; they do not fix the flaws in PHP itself. Have the PHP update installed regardless.
Frequently asked questions about the PHP security update
WordPress and plugins are up to date – is that enough?
No. These updates do not demonstrate that the PHP server runtime has been fixed. The vendor package actually in use must be checked separately.
Cloudflare – am I safe?
Cloudflare can further reduce the risk, but it does not replace the PHP update. For known patterns relating to CVE-2026-126714 and CVE-2026-115560, a PHP RCE rule is also available in the “Free Managed Ruleset”; this ruleset is deployed by default on the Free plan. According to the vendor, this rule is set to “Block” by default. The PHP-FPM rule for CVE-2026-129289 is part of the “Cloudflare Managed Ruleset” for Pro, Business and Enterprise. It initially only logs requests (“Log”) and therefore does not block them itself. For four of the seven critical CVEs, the Cloudflare post reviewed does not specify a dedicated WAF rule. Ask your hosting provider to confirm that your web requests pass through Cloudflare, that the appropriate rules and actions are effective, that exceptions have been reviewed and that the actual web server is not unintentionally accessible directly. Cloudflare DNS alone is not sufficient. Have the PHP update installed regardless.
Static website – does this affect me?
Without PHP execution, this direct attack path is absent. Ask for any PHP forms or administration areas on the same hosting to be checked.
Can every PHP page be exploited immediately?
No. The flaws have different prerequisites. An affected version does not prove that an attack path is reachable on every website.
Is the visible version number enough for backports?
No. The full package/build identifier and vendor evidence are required. The build date alone does not prove that the fix is present.
Has my website already been hacked?
A version number or an attempted attack does not prove this. Ask your hosting provider to check for specific signs of compromise.