Critical, CVSS 4.0 9.2PHPSeven Critical CVEsPHP-FPM

Are your PHP 8.2, 8.3, 8.4 or 8.5 servers still on last month's builds?

PHP released 8.5.13, 8.4.28, 8.3.37 and 8.2.36 on 19 November 2026. This is a security release. PHP 8.6.0, a feature release dated the same day, also includes these fixes. PHP rates seven issues Critical at CVSS 4.0 9.2, including PHP-FPM request smuggling that can lead to unauthenticated code execution, session issues that can lead to remote code execution, and follow-up fixes for incomplete PHP2Shell patches. Upgrade now, then restart PHP workers. Until you can update, apply the vendor workarounds below.

Critical (seven CVEs at CVSS 4.0 9.2, PHP). Released 19 November 2026

php.net dated 8.5.13, 8.4.28, 8.3.37 and 8.2.36 to 19 November 2026. The matching GitHub advisories were published from 14:05 GMT. PHP 8.6.0, a feature release dated the same day, includes the same advisories in its changelog. No exploitation reported as of 19 Nov 2026. None of the new CVE identifiers were in CISA KEV when we checked at 15:05 GMT on 19 November 2026 (catalogue 2026.11.18). Absence from that catalogue is not a finding that the flaws have not been exploited. The earlier PHP2Shell flaws, CVE-2026-109618 and CVE-2026-109619, remain in that catalogue. The 21 October builds (8.5.12, 8.4.27, 8.3.36 and 8.2.35) are no longer sufficient.

At a Glance

Based on PHP's 19 November 2026 changelog and GitHub security advisories, and a CISA KEV check at 15:05 GMT on 19 November 2026. Last updated 19 November 2026, 15:05 GMT.

21 Oct 2026

PHP releases 8.5.12, 8.4.27, 8.3.36 and 8.2.35 for PHP2Shell (CVE-2026-109618 and CVE-2026-109619). Both are later added to CISA KEV.

23 Oct 2026

PHP publishes an advance note on CVE-2026-115560 (session upload progress) and recommends session.upload_progress.enabled=0 until a regular release.

18 Nov 2026

PHP announces a critical security release for 19 November 2026, between 14:00 and 14:30 UTC, covering all supported versions.

14:05 GMT, 19 Nov

PHP publishes 8.5.13, 8.4.28, 8.3.37 and 8.2.36, with advisories from 14:05 GMT, and PHP 8.6.0 as a feature release whose changelog includes the same advisories. This page uses those advisories and the php.net changelog.

What to Do in the Next 24 Hours

Vendor advice and our advice are labelled separately. Tick both tracks.

Proactive: Find Exposure and Patch

Vendor advice is labelled where we are repeating PHP's own guidance. The inventory and prioritisation steps are our advice.

Critical issues (CVSS 4.0 9.2, PHP)

Wording and conditions below are from PHP's own advisories. Scores are CVSS 4.0, as published with each GHSA. We cite those IDs as text.

CVEAdvisoryWhat PHP saysBranches fixed
CVE-2026-129289GHSA-qc49-hpvq-g2w6PHP-FPM request smuggling through an unread HTTP request body. On PHP-FPM, an unauthenticated attacker can make leftover body bytes form a separate FastCGI request and execute PHP code as the worker. This needs persistent backend connections and an application path that opens php://input without reading it fully. PHP says standard nginx and Apache configurations that close the FastCGI connection after each request are not affected by the demonstrated PHP-FPM attack. For LSAPI, the same cleanup error can desynchronise the request stream. The advisory does not establish arbitrary code execution through LSAPI.8.2.36, 8.3.37, 8.4.28, 8.5.13, 8.6.0
CVE-2026-115560GHSA-658j-r8rw-q6mxSession upload progress can write data in one session serialization format and later read it with another, which can lead to remote code execution if the application has a suitable object gadget chain. The mismatch can arise when an application changes session.serialize_handler at runtime, or when separate applications or pools write incompatible data into the same session store. Session upload progress is on by default in affected builds. Set session.upload_progress.enabled=0 administratively. After the update, the feature is disabled by default, but an explicit enable still requires matching serializers.8.2.36, 8.3.37, 8.4.28, 8.5.13, 8.6.0
CVE-2026-126714GHSA-fm2m-fjf5-v3cpThe default files session save handler can leave a session file containing parts of two serialized sessions if a write is interrupted. With a suitable gadget chain, that can lead to remote code execution. Disabling upload progress removes one input path but does not fix applications that independently store untrusted session data.8.2.36, 8.3.37, 8.4.28, 8.5.13, 8.6.0
CVE-2026-129496GHSA-gr4f-wgx5-jpfvTimezone cache use-after-free can lead to remote code execution. The demonstrated trigger needs a startup diagnostic, PHP error logging to a file, and an early request diagnostic in a fresh worker. PHP says code execution has been demonstrated locally in FPM and Apache mod_php with additional assumptions. Until you update, correct configuration errors that produce startup diagnostics and restart the master process and workers, or send PHP errors to a destination such as syslog that does not use this file-timestamp path.8.2.36, 8.3.37, 8.4.28, 8.5.13, 8.6.0
CVE-2026-129474GHSA-8mjj-2r7p-4hg2Use-after-free in magic method backtraces can lead to remote code execution. PHP 8.5 only. The demonstrated remote attack requires fatal_error_backtraces=1 (the 8.5 default) and zend.exception_ignore_args=0. php.ini-production already sets zend.exception_ignore_args=1 and prevents this attack path. Workaround: set zend.exception_ignore_args=1, or set fatal_error_backtraces=0, and restart workers.8.5.13, 8.6.0
CVE-2026-129182GHSA-2fjv-p558-g82mIncomplete fix for PHP2Shell CVE-2026-109619. Use-after-free via repopulation of the last_fatal_error_backtrace global after shutdown. PHP 8.5 only. Temporary workaround: set fatal_error_backtraces=0 and restart workers.8.5.13, 8.6.0
CVE-2026-129481GHSA-g3vh-838c-65v7Incomplete fix for PHP2Shell CVE-2026-109619. Use-after-free after interrupted session shutdown. Affects PHP 8.3, 8.4 and 8.5. PHP 8.2 is not affected, because it does not contain the affected session filename field. Disabling session upload progress does not address this path. Until you update, PHP says avoid fatal errors in callbacks reached during session cleanup. For PHP-FPM, setting pm.max_requests=1 and restarting workers prevents the demonstrated sequence from reaching a second request in the same worker, at a performance cost.8.3.37, 8.4.28, 8.5.13, 8.6.0 (not 8.2)

High and Medium issues in the same release

Also from PHP's advisories. Scores are CVSS 4.0.

  • CVE-2026-129291 (GHSA-jm4m-qfqx-967m), High 8.8: PHP-FPM epoll use-after-free that can lead to local privilege escalation from an FPM worker to the FPM master (often root) when catch_workers_output is enabled. Official PHP-FPM Docker images enable that setting. The default outside such configurations is catch_workers_output=no. The affected path starts at 8.2.7 in the 8.2 branch. Workaround: disable catch_workers_output.
  • CVE-2026-128064 (GHSA-f6gg-rchx-xw8j), High 8.2: mixed-case HTTPS and FTPS URLs, for example HTTPS://, can send data in plaintext. Workaround: use lowercase schemes and do not follow unverified redirects.
  • CVE-2026-127960 (GHSA-mmf9-xm3v-hg2x), High 8.7: denial of service through folded HTTP response headers when PHP's HTTP stream wrapper fetches a URL.
  • CVE-2026-128090 (GHSA-68fq-fh7h-f8gr), High 7.7: PHAR OpenSSL signature bypass via algorithm downgrade, if an attacker can alter a signed archive but not its trusted .pubkey file.
  • Medium issues in the same release include CVE-2026-129538 (PHP-CGI PATH_INFO, 6.9), CVE-2026-129501 (DOM XML serialization double free, 6.3, 8.4 and later), CVE-2026-129506 and CVE-2026-15353 (SOAP, both 6.3), CVE-2026-129292 (FPM status endpoint XSS, 5.3), and CVE-2026-129438 (URI serialization, 6.3, 8.5 and 8.6). 8.5.13 and 8.6.0 also upgrade uriparser (CVE-2026-48841). The detection pack README lists every CVE, score and affected range.

Free Detection Pack

Built by the CybaVerse threat hunt team for businesses, internal IT teams and MSPs. Version 1.0.0 covers the 19 November 2026 PHP security release. Everything is read-only.

Reactive: How to Hunt (Our Advice)

The hunts below are CybaVerse advice, not vendor advice. PHP's advisories describe the flaws and the official mitigations. They do not publish a hunt list.

PHP Security Release FAQ

Short answers based on PHP's 19 November 2026 advisories and a CISA KEV check at 15:05 GMT on 19 November 2026. Last updated 19 November 2026, 15:05 GMT.

Am I affected?

All supported PHP branches are in scope: 8.2, 8.3, 8.4 and 8.5. Upgrade to 8.5.13, 8.4.28, 8.3.37 or 8.2.36. If you are on the 8.6 branch, including an 8.6 pre-release, upgrade to 8.6.0, whose changelog includes the same fixes. Some of the Critical issues need a particular configuration, such as persistent FastCGI connections or session upload progress, and some do not. Treat every internet-facing PHP runtime as in scope until you have updated, including WordPress, LAMP, cPanel and Plesk estates. PHP 8.1 and older are out of official support and are not fixed by this release.

What is the severity?

PHP rates seven issues in this release Critical at CVSS 4.0 9.2: CVE-2026-129289, CVE-2026-115560, CVE-2026-126714, CVE-2026-129496, CVE-2026-129474, CVE-2026-129182 and CVE-2026-129481. The last three were listed less prominently in some early summaries. CVE-2026-129474 and CVE-2026-129182 affect PHP 8.5 only. CVE-2026-129481 affects PHP 8.3, 8.4 and 8.5, not 8.2. There are also four High issues: CVE-2026-129291 at 8.8 (needs catch_workers_output), CVE-2026-127960 at 8.7, CVE-2026-128064 at 8.2 and CVE-2026-128090 at 7.7.

Has this been exploited?

No exploitation reported as of 19 Nov 2026 for the issues fixed in this release. None of these new CVE identifiers were in CISA's Known Exploited Vulnerabilities catalogue when we checked at 15:05 GMT on 19 November 2026 (catalogue version 2026.11.18, released 19:17 GMT on 18 November 2026). Absence from that catalogue is not a finding that the flaws have not been exploited. The earlier PHP2Shell flaws, CVE-2026-109618 and CVE-2026-109619, are already in that catalogue.

What are the fixed versions?

PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36, announced on php.net on 19 November 2026. The GitHub advisories were published from 14:05 GMT. PHP 8.6.0, a feature release dated the same day, also includes the fixes in its changelog. Restart PHP workers after you update. If you use a packaged build from a Linux distribution, cPanel, Plesk or a host, wait for that vendor's build of these versions, then confirm the running version.

What can I do until I can update?

These are vendor workarounds, not a substitute for the update. Disable FastCGI keep-alive or connection reuse (leave nginx fastcgi_keep_conn off, leave Apache mod_proxy_fcgi enablereuse off, and close other FastCGI backends after each request). Set session.upload_progress.enabled=0 administratively, before request input is processed (ini_set() from the application is too late). Use php.ini-production defaults, including zend.exception_ignore_args=1. On PHP 8.5, setting fatal_error_backtraces=0 also blocks the demonstrated paths for CVE-2026-129474 and CVE-2026-129182. For CVE-2026-129291, disable catch_workers_output in affected FPM pools.

How is this related to PHP2Shell?

CVE-2026-129182 and CVE-2026-129481 are incomplete fixes for PHP2Shell issue CVE-2026-109619. Both are rated Critical at CVSS 4.0 9.2. CVE-2026-129182 affects PHP 8.5 only and is fixed in 8.5.13 and 8.6.0. CVE-2026-129481 affects PHP 8.3, 8.4 and 8.5 (not 8.2) and is fixed in 8.3.37, 8.4.28, 8.5.13 and 8.6.0. The 21 October builds (8.5.12, 8.4.27, 8.3.36 and 8.2.35) are no longer sufficient. See our PHP2Shell page for the original flaws, which have confirmed exploitation and are in CISA KEV.

What should I do if I suspect compromise?

This is our advice, not vendor advice. Isolate the host and keep its logs. Restore from a known-good backup or rebuild from a clean, patched image. Rotate application and database secrets, including API keys and session tokens. Updating PHP on a compromised host does not remove an attacker who is already in.

We are an MSP or manage many PHP sites. Where do we start?

Inventory every PHP runtime across hosting, WordPress and LAMP estates. cPanel and Plesk often lag on bundled PHP, so check the running version, not only the package name. Prioritise internet-facing PHP-FPM behind nginx or Apache with connection reuse. Apply the vendor workarounds until the update is installed, then restart workers and confirm the version. Hunt for the signs listed in Our advice. If you need help doing that across the estates you manage, contact CybaVerse.

Need help finding PHP across the estates you manage?

CybaOps monitors your servers, endpoints and cloud workloads, whether that's your own business or your clients'. UK-based analysts monitor alerts 24/7, run these threat hunts and act on pre-approved response actions, and CybaOps drives remediation through to a verified fix, so proactive checks and reactive response happen in one place.

Sources

  1. PHP.net news archive, 2026 (8.5.13, 8.4.28, 8.3.37, 8.2.36 and the 8.6.0 feature release dated 19 Nov 2026; advance notice dated 18 Nov 2026)
  2. PHP 8 changelog (versions 8.5.13, 8.4.28, 8.3.37, 8.2.36 and 8.6.0)
  3. PHP advisories, cited by ID: GHSA-qc49-hpvq-g2w6, GHSA-658j-r8rw-q6mx, GHSA-fm2m-fjf5-v3cp, GHSA-gr4f-wgx5-jpfv, GHSA-8mjj-2r7p-4hg2, GHSA-2fjv-p558-g82m, GHSA-g3vh-838c-65v7, GHSA-jm4m-qfqx-967m, GHSA-68fq-fh7h-f8gr, GHSA-f6gg-rchx-xw8j, GHSA-mmf9-xm3v-hg2x, and the Medium advisories named in the tables above. Published on 19 November 2026 from 14:05 GMT.
  4. CISA Known Exploited Vulnerabilities catalogue (checked 15:05 GMT on 19 November 2026; catalogue version 2026.11.18)