All CVEs

PHP's 19 Nov release (8.6.0, 8.5.13, 8.4.28, 8.3.37, 8.2.36) fixes 17 advisories: 7 critical, 4 high, 6 medium. PHP says every critical one needs a non-default setting or uncommon setup; none is reported exploited, not in CISA KEV, and four have lab or test exploits. Two close gaps in October's exploited PHP2Shell fix. Update and restart workers; until then turn off session upload progress and FastCGI connection reuse. https://tldrcve.com/php-2026-11-19/

PHP · Release roundup · 17 CVEs

PHP Nov release

Patch now if…Roundup17 advisories, 7 critical. All need uncommon setups.

PHP's 19 Nov releases fix 17 security advisories: 7 critical, 4 high and 6 medium (plus a bundled uriparser update, CVE-2026-48841, which is why some count 18). PHP says every critical one needs a non-default setting or an uncommon setup, and none is reported exploited, though four have public lab or test exploits. Two of them close gaps in October's exploited PHP2Shell fix. One update fixes all of them.

How scary is it?

updated 21 Nov
  • Yes: Public exploit code is out8
  • No: No attacks seen yet9,10
  • No: Not on CISA's exploited list11

Scare-o-meter

Check today

Find out if you're affected.
If you are, patch.

The bugs 17 advisories

CriticalSession phpAfterShell: half-written session filesFull page →Patch now if…

PHP's default file session storage can mix an old and a new session when a write is cut short, letting an attacker inject objects. Also needs attacker data in the session, a worker killed mid-write and a usable gadget chain in the app.

CriticalFPM PHP-FPM request smugglingFull page →Patch now if…

An attacker with no login can hide a second request in one web request and run PHP code, but only where the web server reuses its connections to PHP-FPM (off by default in nginx and Apache) and the app leaves part of the request body unread.

CriticalSession Session serializer mismatchFull page →Patch now if…

Upload progress can let an attacker with no login run code, but only where sessions are written with one serializer and read with another, and the app has a usable gadget chain.

CriticalDate Timezone cache use-after-freePatch now if…

Every branch. Needs a non-thread-safe build (PHP-FPM, Apache mod_php or CGI) whose error_log writes to a file, a startup warning written there (for example an invalid date.timezone), and a request to a fresh worker. A request with no login can crash it. A public lab exploit runs code, but reads the worker's memory addresses from inside the lab; PHP calls a remote bypass of that "plausible", not shown.

CriticalEngine Use-after-free in magic method backtracesPatch now if…

PHP 8.5 only, with fatal_error_backtraces on (the 8.5 default) and zend.exception_ignore_args off. That's the built-in default, but php.ini-production turns it on, which blocks this. The app must pass attacker-sized data into a __call() or __callStatic() method so a memory or time limit hits at the right moment, and the attacker needs known memory addresses. PHP confirmed code execution in testing; no code is public.

CriticalSession Use-after-free after interrupted session cleanupNext cycle

PHP 8.3 to 8.5 workers that serve many requests (PHP-FPM or mod_php), with an app callback that runs during session cleanup and that an attacker can make hit a fatal error. A later request on the same worker can then reuse freed memory. One of two gaps PHP found in the October PHP2Shell fix; PHP says code execution hasn't been demonstrated.

CriticalEngine Fatal-error backtrace refilled after shutdownNext cycle

PHP 8.5 only. Needs per-directory settings that change max_memory_limit or zlib output compression, and a later request on the same worker that produces an early warning. The second gap in the October PHP2Shell fix. PHP says code execution hasn't been demonstrated. Workaround: fatal_error_backtraces = 0.

HighFPM PHP-FPM worker to master privilegesPatch now if…

Someone who can already run PHP code in an FPM worker can run commands with the FPM master's privileges, which are commonly root, when catch_workers_output is on. Matters most on shared hosting.

HighStandard HTTPS URLs with an uppercase S sent unencryptedNext cycle

PHP's stream functions such as file_get_contents() sent HTTPS://, httpS:// or FTPS:// URLs without TLS, redirects included, so someone watching the network can read passwords, tokens or uploads.

HighStandard Folded response headers burn CPUNext cycle

A server PHP fetches from can send folded HTTP response headers that tie up the CPU.

HighPhar Signed Phar accepted with a plain hashNext cycle

Someone who can replace an OpenSSL-signed Phar archive, but not its .pubkey file, can swap the signature for a plain hash and still have it accepted.

6 medium: opt-in features or low impact

Are you affected? only if all are true

1PHP older than the 19 Nov 2026 fixcommand

PHP 8.2 to 8.5 below 8.5.13, 8.4.28, 8.3.37 or 8.2.36. PHP 8.6.0 (19 Nov) is fixed. Some bugs only hit 8.3 and later, or only 8.5: see each one. 8.1 and older get no fixes from PHP. Distros may backport fixes without changing the version number.1,3

php -v
2You use an affected featurecommand

Each critical bug needs a specific setting or setup, listed under The bugs above. The main ones: sessions stored in files with upload progress on (phpAfterShell, session serializer mismatch); a web server that reuses its connections to PHP-FPM (request smuggling); a non-thread-safe build logging startup warnings to a file (timezone cache); and PHP 8.5 with fatal error backtraces on (two bugs). Most need workers that serve many requests, which PHP-FPM and mod_php do.2,3,4,5,6,7

php -i | grep -E 'session.save_handler|session.upload_progress.enabled|error_log|fatal_error_backtraces|zend.exception_ignore_args'

What to do

1Update PHP and restart

Update to 8.6.0, 8.5.13, 8.4.28, 8.3.37 or 8.2.36 (19 Nov 2026), then restart every PHP worker. This fixes all 17 advisories.1

Latest safe versions checked 21 Nov

PHP → 8.68.6.08.58.5.138.48.4.288.38.3.378.28.2.36PHP 8.1 and older get no fixes from PHP. Distros may backport fixes without changing the version number.
2Check the critical ones first

phpAfterShell, PHP-FPM request smuggling and PHP session RCE each have a full page with checks. The other four critical bugs and the highs are explained under The bugs above.3

3Can't update yet? Stopgaps

Turn off session upload progress (session.upload_progress.enabled = 0) and FastCGI connection reuse in your web server. On PHP 8.5, set fatal_error_backtraces = 0, or at least keep zend.exception_ignore_args = On as in php.ini-production. These remove some attack paths, not the bugs.3,5,7,9,12

This page shows you how to check. It can't tell you you're safe.

Sources (12) and changelog
  1. PHP: 8.x ChangeLog, 19 Nov 2026 releases and every fix 19 Nov
  2. PHP: 18 Nov notice, critical issues need non-default or uncommon setups 18 Nov
  3. PHP: security advisories (all 17) 19 Nov
  4. PHP GHSA-gr4f: timezone cache use-after-free 19 Nov
  5. PHP GHSA-8mjj: magic method backtraces, 8.5 only 19 Nov
  6. PHP GHSA-g3vh: interrupted session cleanup, incomplete fix for CVE-2026-109619 19 Nov
  7. PHP GHSA-2fjv: backtrace refilled after shutdown, workaround 19 Nov
  8. Public lab exploit for CVE-2026-129496 (reads its own memory map) 19 Nov
  9. Cloudflare Zero Wire: 17 advisories, 7 critical, no exploitation reported 19 Nov
  10. BleepingComputer: counts 18 fixes, no exploitation reported 19 Nov
  11. CISA KEV catalog: none listed
  12. php-src: php.ini-production sets zend.exception_ignore_args = On