Security alert · PHP · 19 November 2026

PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36: seven critical fixes, and who they reach

On Thursday 19 November 2026 the PHP project released PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 as security releases, together with the first general release of PHP 8.6. They fix seven vulnerabilities PHP rates critical, each CVSS v4.0 9.2, and one rated high. The seven include CVE-2026-126714, which the security firm Depthfirst has named phpAfterShell, and CVE-2026-115560, the session flaw PHP announced on 23 October and left for this release. The scores match October’s PHP2Shell, but the reach does not. PHP’s advance notice says the critical issues need a non-default configuration or an uncommon setup, and every advisory lists conditions the attacker cannot supply alone. This page states those conditions for each flaw, shows how to check a server for them, and gives the interim setting for each where the update has to wait. No exploitation of any of them had been reported by 19 November.

Released
19 November 2026, announced from about 14:08 UTC, in PHP’s regular four-week cycle; advance notice on 18 November
Fixed versions
PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36. PHP 8.6.0, released the same day, lists the same fixes in its changelog
Severity
Seven advisories rated critical, CVSS v4.0 9.2; one rated high, 8.8, a local escalation in PHP-FPM. The changelog names ten further CVEs
Conditions
Every critical flaw needs something beyond a request: file sessions that the application opens, a kept-alive FastCGI connection, PHP 8.5, or a particular configuration error
Exploitation
None reported as of 19 November 2026. Depthfirst published a harmless proof and a demo video for phpAfterShell and withheld the full chain
If you cannot update
session.upload_progress.enabled=0, no reuse of FastCGI backend connections, and on 8.5 zend.exception_ignore_args=1; each covers one flaw, none all

Start here

The short version: the same scores as PHP2Shell, with conditions attached

On 18 November the PHP security team announced security releases for the next day. The notice said they would “address security vulnerabilities affecting all supported PHP versions”, that “the highest severity is CRITICAL”, and that “the issues rated CRITICAL require either non-default configuration or uncommon setups”. The releases arrived on schedule on 19 November: 8.2.36, 8.3.37, 8.4.28 and 8.5.13, each announced with the words “This is a security release.” PHP 8.6.0 came out the same day as a new major version. Its announcement does not mention security, but its changelog carries every fix listed here.

That notice is the main difference from 21 October. The two PHP2Shell flaws were reachable on an ordinary installation, PHP said no complete mitigation existed, and both were exploited within days. This time PHP published no separate security advisory on php.net. Each flaw has an advisory on GitHub with its own list of preconditions, and the changelog links them. Seven are rated critical because the result, where the conditions hold, is code execution as the PHP worker without a login. Most servers will meet the conditions for some of them and not others.

For a WordPress server the practical reading is this. WordPress Core does not use PHP sessions, which keeps a plain site away from the three session flaws; plugins that call session_start() bring the site back in. The request-smuggling flaw depends on how the web server talks to PHP-FPM, not on WordPress. Two flaws exist only in PHP 8.5. One needs a startup error written to a log file. The fix is the same in every case: a new PHP package from whoever operates the server, and a restart.

Figure 1 · The PHP releases of 19 November at a glance

Seven critical fixes, each with a condition a server can check.

QuestionWhat the sources sayWhat to do
PatchPHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36; 8.6.0 has the same fixesInstall the package, then restart PHP-FPM or Apache
SeveritySeven critical flaws at CVSS 9.2, one high; all need extra conditionsUpdate this week; check the conditions today
phpAfterShellFile sessions, upload progress and an app that opens sessionsKeep session.upload_progress.enabled at 0
Request smugglingOnly where nginx or Apache reuses FastCGI connectionsTurn fastcgi_keep_conn and enablereuse off
PHP 8.5 onlyTwo engine flaws through fatal-error backtracesSet zend.exception_ignore_args to 1
ExploitationNone reported; a harmless proof for phpAfterShell is publicShared hosts first: one flaw gives local root
What PHP’s advisories and Depthfirst published about the releases of 19 November 2026, and what each item means for a WordPress or server operator.

What PHP has confirmed

Seven critical and one high-severity flaw, fixed in 8.5.13, 8.4.28, 8.3.37 and 8.2.36 on 19 November. Three are in the session extension, two in the engine of PHP 8.5, two in PHP-FPM and one in the date extension.

What is different from October

Each critical flaw needs a non-default configuration or an uncommon setup, in PHP’s words. Nothing has been reported exploited, and every advisory names a setting that closes its own path until the update is in.

What changes in behaviour

According to the advisory for CVE-2026-115560, the fixed releases turn session upload progress off by default and refuse runtime changes to session settings while it is on. An application that shows upload progress through PHP sessions must now enable the feature explicitly.

What you must do now

Update each branch and restart the workers, check the handful of settings that decide exposure, and keep upload progress off wherever it is not needed. PHP 8.2 gets its last fixes on 31 December 2026.

The eight advisories

Each flaw, what it needs, and where it is fixed

The table follows PHP’s GitHub advisories, all published on 19 November. Scores are CVSS v4.0. “All four” means the releases 8.2.36, 8.3.37, 8.4.28 and 8.5.13. The conditions column is the one to read: it decides whether a server is exposed.

The changelog lists ten more CVEs in the same releases, which this page does not analyse: CVE-2026-129538 in the CGI SAPI, CVE-2026-129292 in PHP-FPM, CVE-2026-128090 in Phar, CVE-2026-15353 and CVE-2026-129506 in SOAP, CVE-2026-128064 and CVE-2026-127960 in the standard library, CVE-2026-129501 in DOM (8.4 and later), and CVE-2026-129438 and CVE-2026-48841 in the URI extension (8.5 and later). That makes twelve CVE entries in 8.2.36, thirteen in 8.3.37, fourteen in 8.4.28 and eighteen in 8.5.13.

PHP 8.6.0 needs a note. None of the advisories we read names it as a patched version, because 8.6.0 is the first release of its branch and there is no earlier 8.6 to be vulnerable. Its changelog lists every fix. A server on an 8.6 release candidate should move to 8.6.0.

Flaw and fixWhere and whatWhat an attacker needs
CVE-2026-126714, phpAfterShell. CVSS 9.2. Fixed in all fourSession extension, the files save handler. A session file is written over the old one without being emptied first, so an interrupted write leaves the start of the new data joined to the end of the oldFile-based sessions (PHP’s default), influence over session data, a write interrupted at a useful point, and a session the application later opens. The advisory also requires a deserialization gadget chain in the application; Depthfirst says its chain needs none
CVE-2026-115560. CVSS 9.2. Fixed in all fourSession extension, upload progress. Session data written under one serializer is read back under another, which turns attacker-supplied text into objectsUpload progress enabled, a context that writes sessions with php_binary or php_serialize, the same session read later with the php serializer, and a gadget chain. PHP calls this setup unlikely
CVE-2026-129289. CVSS 9.2. Fixed in all fourPHP-FPM, and LSAPI to a lesser degree. Bytes of a request body the script did not read are taken as the next FastCGI requestA front end that reuses backend connections (nginx fastcgi_keep_conn on, Apache mod_proxy_fcgi with enablereuse=on, HAProxy keeping connections) and a script that opens php://input without reading it to the end. No login, no race
CVE-2026-129496. CVSS 9.2. Fixed in all fourDate extension. A use-after-free in the timezone cache that workers inherit from the parent processA non-thread-safe build and a diagnostic at startup written to a file-based error log, for example an invalid date.timezone. A crafted request then crashes a worker; code execution was shown only locally with known addresses
CVE-2026-129481. CVSS 9.2. Fixed in 8.3.37, 8.4.28 and 8.5.13; 8.2 is not listed as affectedSession extension. A use-after-free after session shutdown is interrupted; the advisory calls it an incomplete fix for CVE-2026-109619A fatal error inside an application callback during session cleanup, then a second request to the same worker. Upload progress is not needed. Code execution has not been demonstrated
CVE-2026-129474. CVSS 9.2. Fixed in 8.5.13Engine, PHP 8.5 only. A use-after-free when a fatal-error backtrace collects the arguments of __call() or __callStatic()fatal_error_backtraces=1 and zend.exception_ignore_args=0, a reachable magic method, a fatal error at the right point and control over memory layout. php.ini-production sets exception_ignore_args to 1, which blocks it
CVE-2026-129182. CVSS 9.2. Fixed in 8.5.13Engine, PHP 8.5 only. A use-after-free in the fatal-error backtrace global, a follow-on to the 8.5.12 fixOne of two specific combinations of global and per-path settings (max_memory_limit, or zlib.output_compression with an output_handler) plus a diagnostic before a later request initialises. Crashes were shown; code execution was not
CVE-2026-129291. CVSS 8.8. Fixed in all four; affects 8.2.7 and laterPHP-FPM. A use-after-free in the epoll event handling of the master process, giving local privilege escalationCode already running in an FPM worker, catch_workers_output enabled, the epoll backend, and control over worker lifetimes. Where the master runs as root, the pool user becomes root

CVE-2026-126714

phpAfterShell: an interrupted file write becomes a forged session

PHP’s default session storage is one file per session. When a request ends, PHP writes the new session data at the start of that file with pwrite() and then cuts the file to the new length with ftruncate(). The two steps are not atomic, and the file lock does not make them so. If the worker dies between them, or partway through the write, the file holds the beginning of the new session followed by whatever remained of the old one.

Depthfirst’s research shows how to make that useful. PHP’s session format stores each value with its length. An attacker who controls a long string in the old session and the length fields at the start of the new one can arrange the join so that bytes which were harmless text inside a string are read as separate session entries, including serialized objects. Nothing is deserialized during the write. The file waits on disk until the application calls session_start() for that session, and PHP then builds the objects. Depthfirst describes it this way: “If a pwrite()/ftruncate() update is interrupted, PHP may leave behind a malformed session file that is later loaded by session_start(), yielding an arbitrary deserialization primitive.”

The easiest way to write into a session without a login is session upload progress. With that feature on, PHP updates a file-backed session while it parses a multipart upload, before any application code runs. Depthfirst’s post lists the preconditions for this path as a multipart request with upload progress enabled, session.save_handler set to files, a worker interrupted during the update, and a known session ID. PHP’s advisory names two more ways to reach the same write: large user-controlled strings that an application stores in the session, and, in threaded builds, a hard memory-limit failure in another thread.

The fix empties the session file before writing and aborts if that fails. Both PHP and Depthfirst say that disabling upload progress removes the easiest path but not the flaw, since an application that stores attacker-controlled data in sessions can still be driven to the same state. Sessions kept in Redis, a database or another handler that replaces a record in one step are not affected by this defect, according to Depthfirst.

PointPHP’s advisoryDepthfirst
From forged session to code executionRequires a usable deserialization gadget chain in the applicationThe research post says the full chain does not depend on an application-defined gadget class and uses a memory-corruption bug in a PHP-native class; its summary page says a suitable gadget chain is required
Fixed versions8.2.36, 8.3.37, 8.4.28 and 8.5.13The summary page gives the same four. The research post’s table, dated 17 November, still marks the 8.4.28, 8.5.13 and 8.6.0 release candidates as vulnerable to one variant
Who reported itThe GitHub advisory credits the handle zplinn; the CVE record credits Leo Lin and AsahiThe research post is written by Yuhang Wu and says the team reported the flaw privately in late October
Older branchesLists 8.2.0 onward; PHP does not assess end-of-life branchesSays the 7.4, 8.0 and 8.1 backport branches PHP published in October are not affected

Who is exposed

What a WordPress server has to look like for each flaw to matter

None of PHP’s advisories or Depthfirst’s pages mentions WordPress. The reading below is ours, made by setting each advisory’s conditions against how WordPress servers are commonly built.

One point about the session flaws is not settled by the sources. Upload progress writes the session file without any help from the application, so the corrupted file can be created on a site that never uses sessions. It becomes dangerous only when something calls session_start() for that session. On a WordPress site with no session-using plugin that second step has no obvious trigger, which is why we rate such a site as low exposure to phpAfterShell and not as out of scope. A plugin installed next month can supply the missing step, and the fix removes the question.

The local escalation deserves more attention on shared hosting than its lower score suggests. It turns code execution as one site’s user into root where the FPM master runs as root, which is the usual arrangement. October’s PHP2Shell exploitation was chained with a kernel flaw for the same purpose. An attacker holding a web shell on one account now has a second route.

If the server hasFlaw in reachHow common on WordPress hosting
File-based sessions, upload progress on, and a plugin or theme that calls session_start()phpAfterShell, CVE-2026-126714Common. Files are PHP’s default handler and upload progress was on by default until these releases. WordPress Core opens no session, but shop, membership, form and login plugins often do, and Site Health reports it as “An active PHP session was detected”
Sessions written under one serializer and read under anotherCVE-2026-115560Rare. It needs a runtime ini_set() of session.serialize_handler, or two applications or pools with different settings sharing one session directory. A shared /tmp or /var/lib/php/sessions across pools makes the second case possible
nginx with fastcgi_keep_conn on, Apache with enablereuse=on, or HAProxy keeping FastCGI connectionsCVE-2026-129289, request smugglingUncommon but deliberate. Both settings are off by default; they are switched on in performance tuning, usually with an nginx upstream keepalive block. LiteSpeed’s LSAPI is affected by the desynchronisation without code execution
PHP 8.5CVE-2026-129474 and CVE-2026-129182Limited to sites already on 8.5. The first is blocked by zend.exception_ignore_args=1, which php.ini-production sets; a server built from php.ini-development or without a php.ini has it at 0
A startup warning in a file-based PHP error logCVE-2026-129496Easy to overlook. An invalid date.timezone or a deprecated setting left in php.ini after a version change is enough, and the warning repeats at every restart
Callbacks that can fail fatally during session cleanupCVE-2026-129481Application-specific: custom session handlers and stream wrappers. PHP 8.3 and later only
Shared hosting or containers where one pool’s code is untrusted, with catch_workers_output onCVE-2026-129291, local rootThe official Docker images turn output capture on by default, and the advisory reports a root proof of concept against them. On shared hosting any compromised site supplies the code execution this flaw starts from

Check your server

Read-only checks for the settings that decide exposure

These commands read configuration and change nothing. Run them for every PHP branch a site uses, not only the server default, and from the server itself. The command-line interpreter reads its own php.ini, so where a value matters, confirm it from the web side as well: in WordPress at Tools, Site Health, Info, Server, or with a temporary phpinfo page that you delete afterwards.

  1. 01

    List every PHP branch and its session settings

    The version, the session handler, the serializer and whether upload progress is on, for each interpreter the server has:

    shell
    for p in /usr/bin/php /usr/bin/php8.* /opt/cpanel/ea-php*/root/usr/bin/php /opt/alt/php*/usr/bin/php; do [ -x "$p" ] && echo "$p $($p -r 'echo PHP_VERSION, " handler=", ini_get("session.save_handler"), " serializer=", ini_get("session.serialize_handler"), " upload_progress=", ini_get("session.upload_progress.enabled");')"; done

    A branch below 8.5.13, 8.4.28, 8.3.37 or 8.2.36 needs the update, unless its package changelog lists the CVEs. handler=files with upload_progress=1 is the phpAfterShell path. A serializer other than php on any branch is the first half of CVE-2026-115560.

  2. 02

    Find the plugins and themes that open a session

    From the WordPress root of each site:

    shell
    grep -rlE 'session_start[[:space:]]*\(' wp-content/plugins wp-content/mu-plugins wp-content/themes --include='*.php' | cut -d/ -f2-3 | sort | uniq -c

    Each line is a plugin or theme with a session_start() call somewhere in its code. Not every call runs on every request, but a site with any of them should be treated as using sessions.

  3. 03

    Check whether the web server reuses FastCGI connections

    For nginx, then for Apache:

    shell
    nginx -T 2>/dev/null | grep -nE 'fastcgi_keep_conn|keepalive [0-9]'
    grep -RnE 'enablereuse' /etc/apache2 /etc/httpd /usr/local/apache/conf 2>/dev/null

    fastcgi_keep_conn on, or enablereuse=on, puts the server in scope for the request-smuggling flaw. No output from both commands means connections are not reused, which is the default.

  4. 04

    Check the FPM pools for output capture and listeners

    The settings behind the local escalation, and where each pool listens:

    shell
    grep -RnE '^[[:space:]]*(catch_workers_output|events\.mechanism|listen)[[:space:]]*=' /etc/php/*/fpm /etc/php-fpm.d /etc/php-fpm.conf /opt/cpanel/ea-php*/root/etc/php-fpm.d /usr/local/etc/php-fpm.d 2>/dev/null

    catch_workers_output = yes is the condition for CVE-2026-129291. A listen value that is a TCP address other than 127.0.0.1 means the pool is reachable over the network, which the smuggling advisory warns against.

  5. 05

    On PHP 8.5, read the two backtrace settings

    Substitute the path of the 8.5 interpreter:

    shell
    php8.5 -i | grep -E 'fatal_error_backtraces|zend.exception_ignore_args'

    fatal_error_backtraces On together with zend.exception_ignore_args Off is the combination CVE-2026-129474 needs.

  6. 06

    Look for startup diagnostics in the PHP error log

    Warnings that PHP writes when it starts are the condition for CVE-2026-129496:

    shell
    grep -hE 'PHP (Warning|Deprecated|Notice):.*(Unknown|date\.timezone|session\.|Directive)' /var/log/php*-fpm.log /var/log/php-fpm/*.log /var/log/apache2/error.log /var/log/httpd/error_log 2>/dev/null | sort | uniq -c | sort -rn | head

    Adjust the paths to where your pools log. A line that repeats at each restart points to a php.ini or pool setting to correct; the advisory’s mitigation is to fix the cause and restart the master and its workers.

Update now

Fixed packages on each stack, as of 19 November

Source and Windows builds are on php.net. Everything else arrives through a vendor, on the vendor’s schedule. The table records what each vendor’s own page showed on 19 November; rows marked as not confirmed are ones we could not verify, not ones known to be late.

  1. 01

    Update, then restart

    A package update replaces files on disk. Workers that are already running keep the old code until they restart, and with mod_php that means Apache itself. Use the unit names your server has:

    shell
    systemctl restart php8.4-fpm
    systemctl restart apache2

    On cPanel, restart PHP-FPM and Apache through WHM or its restart scripts. Then confirm the version from the web side, one site per branch.

  2. 02

    Check what the update changed in session behaviour

    According to the advisory for CVE-2026-115560, the fixed releases disable session upload progress by default and reject runtime changes to session settings while it is enabled. Two things follow. A php.ini, pool file or per-domain setting that turns the feature on explicitly overrides the new default, so search for one. And an application that calls ini_set() on session settings may now log a warning where it did not before; watch the error log for a day after the update.

  3. 03

    Plan the end of PHP 8.2

    PHP 8.2 leaves security support on 31 December 2026, and 8.2.36 may be among its last releases. PHP 8.3 is in security-only support until the end of 2027. A site moved to 8.2 as a safe choice two years ago needs its next move scheduled now.

Where PHP comes fromStatus on 19 NovemberWhat to do
php.net source and Windows builds8.5.13, 8.4.28, 8.3.37, 8.2.36 and 8.6.0 releasedRebuild or replace, then restart
Debian 13php8.4 8.4.28-1~deb13u1, security advisory DSA-6641-1Run apt update and apt upgrade, then restart php8.4-fpm or Apache
Debian 12php8.2 8.2.36-1~deb12u1 is in bookworm-security; the security tracker still showed the CVEs as open when we lookedUpgrade, then confirm the installed package version
UbuntuCVE-2026-126714 published with priority Medium; every release “Needs evaluation”, including php8.3 on 24.04 and php8.1 on 22.04Apply the interim settings below and watch the Ubuntu CVE page
cPanel EasyApache 4Version 25.98, dated 19 November: ea-php82 8.2.36, ea-php83 8.3.37, ea-php84 8.4.28, ea-php85 8.5.13. The entry names no CVEs and no older branchesUpdate the ea-php packages, then check which sites still select 8.1 or older
Docker official imagesTags for 8.5.13, 8.3.37 and 8.6.0 pushed on 19 November; 8.4.28 and 8.2.36 not checkedRebuild from the new tag and redeploy. Restarting an old container changes nothing
Red Hat, CloudLinux alt-php, Plesk, the Sury packagesNot confirmed: no statement found or the page could not be readCheck the vendor’s advisory page and the package changelog for the CVE numbers

If you cannot update yet

The interim setting for each flaw, and what each leaves open

Each setting below comes from the advisory for the flaw it addresses. Set them in php.ini, an FPM pool file or the web server configuration and restart the workers. ini_set() in application code is too late for the session settings, as the CVE-2026-115560 advisory says in those words, and a change to the command-line php.ini alone does not reach the web workers.

  1. 01

    Session flaws: keep upload progress off

    For phpAfterShell and CVE-2026-115560:

    php.ini, or a PHP-FPM pool file
    ; php.ini or a conf.d drop-in
    session.upload_progress.enabled = 0
    
    ; PHP-FPM pool
    php_admin_flag[session.upload_progress.enabled] = off

    This is the setting PHP has asked for since 23 October. It closes the unauthenticated upload path. It does not protect an application that itself stores attacker-controlled data in sessions, and it does nothing for CVE-2026-129481, where the advisory says upload progress is not involved. WordPress does not use the feature, so the setting costs a WordPress site nothing.

  2. 02

    Request smuggling: stop reusing backend connections

    For CVE-2026-129289, turn off connection reuse between the web server and PHP-FPM:

    nginx and Apache
    # nginx, in the location that passes to PHP
    fastcgi_keep_conn off;
    
    # Apache mod_proxy_fcgi: remove enablereuse=on, or set
    # enablereuse=off on the ProxyPass or SetHandler proxy line

    Reload the web server afterwards. The cost is a new connection to PHP-FPM per request, which is how most servers already run. The advisory also lists reading php://input to the end in every script, and says that alone may be unreliable. Keep FPM and LSAPI listeners off untrusted networks.

  3. 03

    PHP 8.5: hide arguments in backtraces

    For CVE-2026-129474, and with the second line for CVE-2026-129182:

    php.ini, PHP 8.5
    zend.exception_ignore_args = 1
    fatal_error_backtraces = 0

    Either line blocks CVE-2026-129474; the second is the advisory’s mitigation for CVE-2026-129182. Setting display_errors to 0 does not help.

  4. 04

    Timezone flaw: remove the startup warning

    For CVE-2026-129496, correct the setting that makes PHP log a diagnostic when it starts, then restart the master and the workers. The advisory’s alternative is to send the error log to syslog or another destination that is not a file.

  5. 05

    Local escalation: turn off output capture where pools are untrusted

    For CVE-2026-129291, the advisory’s mitigation is to disable catch_workers_output in the affected pools. In a container that relies on it to send application output to the container log, that output goes missing, so weigh it against how long the update will take. Running the FPM master without root limits what the flaw can reach.

  6. 06

    Session cleanup flaw: no clean setting

    For CVE-2026-129481 the advisory offers pm.max_requests = 1 in PHP-FPM, which stops a worker from serving a second request and prevents the demonstrated sequence. It respawns a worker per request and is a measure for hours on a busy site, not days.

Actions

The actions, in priority order

Update first where a fixed package exists. Where it does not, the order below puts the widest exposure first.

  1. 01

    Update every branch a site uses, and restart

    Install 8.5.13, 8.4.28, 8.3.37 or 8.2.36 or the vendor package that carries the fixes, restart PHP-FPM or Apache, and confirm the version from the web side. Do it per site: a cPanel server with ea-php84 updated still runs every site that selects another branch through that branch’s package.

  2. 02

    Keep session upload progress off

    Leave session.upload_progress.enabled at 0 on every branch and pool, before and after the update, unless an application needs the feature. After the update, check that nothing sets it back on explicitly.

  3. 03

    Check how the web server talks to PHP-FPM

    If fastcgi_keep_conn or enablereuse is on, the server is in scope for unauthenticated request smuggling. Update first on those servers, or turn reuse off today.

  4. 04

    On PHP 8.5, confirm the php.ini in use

    A server started from php.ini-development, or with no php.ini at all, has zend.exception_ignore_args at 0. Set it to 1.

  5. 05

    Clear startup warnings from the PHP error log

    They are the condition for the timezone flaw, and they are configuration errors worth fixing in any case.

  6. 06

    On shared hosting and in containers, treat the local escalation as urgent

    Any compromised site on the server is the starting point for CVE-2026-129291. Update the FPM packages on multi-tenant servers ahead of single-site ones.

  7. 07

    Ask your provider

    On managed or shared hosting, ask which PHP branches have the 19 November fixes, when the workers were restarted, and what is planned for sites on 8.1 or older.

Sources

Where every claim on this page comes from

The release dates, the announcement wording and the advance notice come from php.net’s news archive and the php.announce list. The list of fixes per version comes from the PHP 8 changelog. For each of the eight flaws, the title, the score, the affected and fixed versions, the preconditions, the mitigations and the credits come from PHP’s advisory on GitHub, published on 19 November. The description of phpAfterShell comes from Depthfirst’s research post by Yuhang Wu and its summary page. The package status comes from each vendor’s own page as it stood on 19 November. The Hacker News article we were pointed to was written before the release and covers the advance notice and CVE-2026-115560; it reports no exploitation of these flaws.

Three limits apply. We read the advisories through a retrieval tool that returned some passages as summaries, so apart from PHP’s advance notice and the Depthfirst sentence, this page paraphrases them and does not quote them. We did not read the ten further advisories named in the changelog. And the reading of what each flaw means for a WordPress server is ours; no source cited here discusses WordPress. Exploitation status is as of 19 November 2026. If that changes, this page and the weekly briefing will say so.

Common questions

Common questions about the November 2026 PHP security releases

Is this as serious as PHP2Shell?

The scores are the same, 9.2, but the reach is narrower. PHP2Shell worked against ordinary installations and was exploited within days. PHP says each critical flaw in this release needs a non-default configuration or an uncommon setup, and none had been reported exploited by 19 November 2026. Treat it as an update for this week, and for today on servers that reuse FastCGI connections or host many tenants.

What is phpAfterShell?

Depthfirst’s name for CVE-2026-126714. PHP wrote a session file over the old one without emptying it first, so a worker killed during the write left a file made of the new data’s start and the old data’s end. With chosen lengths, an attacker can make that mixture decode as serialized objects the next time the application opens the session. It is fixed in 8.5.13, 8.4.28, 8.3.37 and 8.2.36.

Does this affect WordPress?

Through the server, in different degrees. WordPress Core does not use PHP sessions, so a plain site is far from the three session flaws; a plugin that calls session_start() changes that. The request-smuggling flaw depends on the web server’s FastCGI settings, the two engine flaws on PHP 8.5, and the local escalation on PHP-FPM’s output capture. None of them can be fixed from inside WordPress.

I set session.upload_progress.enabled to 0 in October. Am I covered?

For the upload-progress path of phpAfterShell and for CVE-2026-115560, yes, provided the setting is in php.ini or the pool and the workers were restarted. Not for the other five critical flaws, and not for an application that stores untrusted data in its sessions. You still need the update. Keep the setting afterwards; the fixed releases make it the default.

My distribution’s PHP still shows an older version number. Is it vulnerable?

Not necessarily. A distribution security update usually keeps its version string and adds the fix, as Debian and Ubuntu did in October. Check the package changelog or the distribution’s advisory for the CVE numbers. On 19 November Debian had fixed packages for php8.4 and php8.2, and Ubuntu listed its releases as needing evaluation.

Are PHP 7.4, 8.0 and 8.1 affected?

PHP does not say; its advisories list only supported branches. The request-smuggling advisory dates its cause to PHP 5.6.0, so assume old branches share that flaw. Depthfirst says the 7.4, 8.0 and 8.1 backport branches from October are not affected by phpAfterShell. For a vendor-maintained package, the vendor’s changelog is the only reliable answer.

Should I move to PHP 8.6?

Not because of this release. 8.6.0 contains the same fixes as 8.5.13 and is a new major version, with the plugin and theme compatibility questions any such version brings. Update the branch you are on now, and test 8.6 on a staging copy when your plugins declare support for it.

Choose the response path

PHP is updated and you are not sure which of the seven conditions applied: choose the response path.

Many sites, several PHP branches

Get each site’s PHP branch, pool and session settings checked in one pass.

Best when a server runs several PHP versions, you cannot say which sites use sessions or how the web server connects to PHP-FPM, and you want the version, the handler, the pool settings and the restart confirmed per site with a written result.

Something already looks wrong

A PHP worker running a shell, a file you did not upload, or a root process you cannot explain.

Best when the server was exposed and you have found a process, a file or an account that should not be there, and you want the compromise scoped, the persistence removed and the server returned to a trusted state.