Skip to content
All posts

Laravel & PHP7 min read

PHP's Nov 19 Security Fix: Is Your Laravel App Affected?

PHP 8.2 to 8.5 got fixes on Nov 19 for seven critical flaws that need uncommon setups. How to check your Laravel servers, then patch.

By Aymen Meziani

On this page

PHP shipped security releases for every supported branch on Nov 19: 8.5.13, 8.4.28, 8.3.37 and 8.2.36. They fix 17 flaws in PHP itself, plus one in the uriparser library it uses. Seven are rated critical, each 9.2 on CVSS v4.0. PHP 8.1 and older got no release.

The day before, PHP's announcement said the critical issues "require either non-default configuration or uncommon setups". The details bear that out. Each critical flaw needs a specific setting, a specific server setup or PHP 8.5. So the first job is to find out whether any of your servers match. The patch comes right after.

This post covers the flaws that matter for a Laravel app, the checks that tell you whether you are exposed, and what patching took on the platforms we run.

What the Nov 19 release fixes

Four of the critical flaws are the ones to read first, because their conditions can occur on a normal web server:

CVEPart of PHPWhat it needs
CVE-2026-129289PHP-FPMA web server that keeps FastCGI connections open between requests, and an app that leaves part of a request body unread
CVE-2026-115560SessionsSession upload progress turned on (PHP's default), and an app that writes sessions with one serializer and reads them with another
CVE-2026-126714SessionsPHP's default file session handler, session data an attacker controls, a write interrupted at the wrong moment, and a class in the app that can be abused
CVE-2026-129474Core, PHP 8.5 onlyA fatal error inside __call() or __callStatic(), with fatal error backtraces on and function arguments kept in them

Sources: Aikido, Semgrep and the Laravel Forge advisory. The other critical flaws need rarer combinations, such as file-based error logging with startup diagnostics turned on.

The flaws rated lower matter too. They include a use-after-free in PHP-FPM's event loop (8.8), a crash on folded HTTP headers (8.7) and HTTPS URLs written in mixed case being fetched in plain text (8.2). These are the reason to patch every server, exposed or not.

None of the sources we read reported attacks in the wild by Nov 20. If you skipped the Oct 21 PHP2Shell fixes, you have both to install. We covered them in PHP2Shell: patch today, or upgrade first?

Is your Laravel app affected?

Run these checks on each server or container that serves web requests. They take about 5 minutes per server.

  1. FastCGI connection reuse: run grep -rn fastcgi_keep_conn /etc/nginx/, and the same inside any nginx container. nginx closes the FastCGI connection after each request unless this is set to on, so most Laravel setups do not meet the condition for CVE-2026-129289. On Apache, look for enablereuse=on. If you find either, turn it off until PHP is patched.

  2. Native PHP sessions: as we read Laravel's session code, its drivers (file, database, Redis, cookie) store sessions through Laravel's own classes and do not call session_start(). The session flaws sit in PHP's native session functions, so the risk is older PHP code on the same server: a legacy admin panel, a WordPress install, or a package that starts a native session. Search for session_start( and ini_set('session..

  3. Upload progress: run php -i | grep session.upload_progress.enabled. Laravel does not use the feature. Until you patch, set it to 0 in php.ini or the PHP-FPM pool file and restart PHP-FPM. Setting it with ini_set() or a .user.ini file does not work for this.

  4. PHP 8.5: check zend.exception_ignore_args and fatal_error_backtraces. PHP's production php.ini sets the first to On, which closes CVE-2026-129474, and so does setting the second to 0. Docker images that start from the development php.ini, or from none, may leave both open.

  5. The version that runs: check PHP-FPM, not only php -v. The command-line PHP and PHP-FPM can be different builds. Repeat for staging, queue workers, cron servers and CI images.

If none of your servers match, the critical flaws do not reach you. Patch this week anyway, for the flaws rated lower.

Patch today or this week

flowchart LR
  A[Run the checks] --> B{Any server matches?}
  B -- Yes --> P[Mitigate, patch today]
  B -- No --> N[Patch this week]
  P --> C{PHP 8.2?}
  N --> C
  C -- Yes --> U[Upgrade by Dec 31]
  C -- No --> D[Done]

A server that matches should get the setting change now and the patch the same day. After PHP2Shell in October, attacks started within hours of the details going public, and the details of these flaws are public too.

A server that does not match can take the patch with your next regular deploy this week. That avoids a rushed release on a busy day.

How to patch without breaking the app

  1. Install the patched build from the same source you installed PHP from: your Linux distribution, Ondřej Surý's packages, Remi's repository or the official Docker image.

  2. Read the package changelog when the version looks old. Ubuntu 24.04's own PHP stays at 8.3.6 with the fixes backported. Run zcat /usr/share/doc/php8.3-common/changelog.Debian.gz | head -60 and look for the CVE numbers.

  3. Move pinned Docker images. If your Dockerfile says FROM php:8.4.27-fpm, rebuilding pulls 8.4.27 again. Change the tag to 8.4.28, along with the image your CI tests on, so tests run on the PHP you deploy.

  4. Restart every PHP process: PHP-FPM, Horizon or queue workers, Octane workers, and Apache with a full restart if it runs mod_php. Forge's advisory reminds its users that its automatic updates do not patch PHP, and that workers keep the old code until restarted.

  5. Test before the new build reaches production: the test suite on the new image, then login, checkout and any file upload by hand.

  6. Confirm the version from the web server, not only from the command line.

A patch release inside the same branch (8.4.27 to 8.4.28) rarely breaks a Laravel app. When something does break, it is usually a PHP extension that came from somewhere other than the PHP build, so test with the same extensions you run in production.

On PHP 8.2? This is one of its last fixes

PHP 8.2 gets security fixes until Dec 31, 2026. After that, PHP's four-week cycle continues without it. A flaw found in January will be fixed for 8.3 and newer only.

PHP branchSecurity support untilFixed inWhat to do now
8.5Dec 31, 20298.5.13Patch
8.4Dec 31, 20288.4.28Patch
8.3Dec 31, 20278.3.37Patch
8.2Dec 31, 20268.2.36Patch, then upgrade before Dec 31
8.1 and olderEndedNo releaseUpgrade, and isolate the app until then

Dates from php.net supported versions.

Some distributions and community package builds may carry backported fixes for older branches. Check the changelog. A backport closes these flaws. It does not make that version supported, and nothing promises the next fix will be backported.

For upgrades we recommend PHP 8.4 when the app runs Laravel 11, 12 or 13 and its packages allow it. On Laravel 10 the ceiling is PHP 8.3, supported until Dec 31, 2027. We go through the steps in PHP 8.2 end of life: what your Laravel app needs by Dec 31.

What patching took on the platforms we run

Meraki, the learning platform we built and run for a children's language school, serves 2,600+ students. It runs in Docker, so a PHP security fix is a change to the image version, a full test run on the new version, then a deploy. Meraki's deployments are zero-downtime, so students in a lesson do not notice. Read the Meraki case study.

On our other servers, PHP comes from the operating system's packages. There the work was the update, a restart of every PHP-FPM pool and worker, and the changelog check above to confirm the CVE fixes were in the package.

The same week, nginx had its own critical release. If your PHP runs behind nginx, check it too: nginx2root: is the nginx in front of your app patched?

You may not need us for this. If your app is on managed hosting that patches PHP for you and you are on 8.3 or newer, the fix is a support ticket to your host and a quick check afterward.

Next step

Not sure which PHP version each of your servers runs, or what moving off 8.2 would take? Send us your composer.lock and we will do a free upgrade check: your PHP and Laravel versions, what blocks the upgrade, and a fixed quote. Laravel upgrades start from $1k. Book a short intro call.

Keep reading

Running an older Laravel app?

Share your composer.lock and PHP version. We tell you which versions you cross, what blocks you and what drives the cost, before you commit to anything.