deniz.in

Markets

Weather

Loading weather

· via dev.to (home feed)

PHP security update fixes 18 vulnerabilities, two rated 9.2 under CVSS 4.0

PHP's November 19, 2026 security release fixed 18 vulnerabilities, including a session serializer mismatch and a FastCGI request injection flaw, both scored 9.2 under CVSS 4.0.

PHP security update fixes 18 vulnerabilities, two rated 9.2 under CVSS 4.0

On November 19, 2026, PHP shipped a security update that fixes 18 vulnerabilities, and server operators are being urged to move quickly: two of the flaws carry a 9.2 score under CVSS 4.0. According to a dev.to write-up, the critical pair are CVE-2026-115560 and CVE-2026-129289, both resolved in PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36. On PHP 8.1 and older branches, which no longer receive upstream releases, protection depends on backports distributed by vendors.

Two flaws rated 9.2

The first vulnerability is a session serialization problem. It becomes dangerous when session upload progress is enabled and applications that share the same session storage use different serialize handlers — the dev.to article points to a mismatch between php and php_serialize or php_binary. The divergence does not need to occur at runtime: it can exist between applications, FPM pools, virtual hosts or command-line processes, and separate pools do not guarantee separate storage. In a test on Rocky Linux described in the article, two pools sharing /var/lib/php/session with different handlers and upload progress left enabled confirmed the exposure without any change to application code.

The second flaw allows injecting a request into a FastCGI connection. It requires two conditions at the same time: the front-end server keeps the FastCGI connection to PHP-FPM open between requests, and an application path opens php://input without reading the entire body. Leftover bytes can then be interpreted as the start of a new request.

Defaults decide exposure

For the FastCGI flaw, web server configuration largely determines whether a site is exposed. According to dev.to, nginx keeps fastcgi_keep_conn off by default; Apache can enable connection reuse with enablereuse=on; and HAProxy turns keep-conn on by default within an fcgi-app section. PHP's guidance also lists LiteSpeed as affected. The article recommends searching nginx and Apache configuration files for the relevant directives and using nginx -T to inspect the configuration the service actually loaded.

Patches are uneven across distributions

In checks run on November 19 and 20, fixed packages were available in the Remi repositories, Debian Security, Debian LTS, the ondrej/php PPA, Amazon Linux and the official Docker images. Alpine had the fix in its edge channel but not in the stable releases consulted, while Ubuntu's default archive did not yet carry fixed builds even as PPA packages were being published.

Ubuntu adds a version-number trap: on 24.04, PHP 8.3 can continue to report 8.3.6 after a backported fix is installed, so operators should verify the installed package and its changelog rather than trust the version string alone.

Red Hat's PHP streams for RHEL 8, 9 and 10 appeared affected with no fix available at the time of the checks. Red Hat classified both flaws as critical and stated that the session issue does not apply to the RHEL 9 PHP 8.0 and RHEL 8 php:7.4 streams because earlier updates disabled upload progress — even though its VEX data still listed them as affected. Those two streams remain exposed to the other vulnerabilities in the batch.

Check the PHP that actually serves requests

The PHP available at the terminal can be fully up to date while the PHP-FPM process handling site traffic is still vulnerable, dev.to cautions. The article recommends checking the FPM binary, the installed packages and the response of the running pool rather than relying solely on the output of php -v.

No known exploitation yet

As of November 20, 2026, the article reports no real-world exploitation. The CISA KEV catalog did not list the CVEs, FIRST's EPSS had no score for them, and NVD showed both as awaiting analysis. The absence of those records, the author notes, does not remove the risk on servers where the vulnerable conditions are present.

Why it matters

Two near-top-severity flaws in a single release, affecting one of the most widely deployed server-side runtimes, is the kind of update that deserves a short patch timeline. The practical difficulty is that exposure depends on configuration — shared session storage with mixed serializers, or persistent FastCGI connections — so some operators may not realize they are affected until they audit their setups. Distribution coverage is also patchy: Ubuntu's main archive and Red Hat's streams lagged behind at the time of the checks, and Ubuntu's backport versioning makes patch state hard to read from a version number alone. The safe sequence is to install a fixed build where available, verify which PHP binary actually answers requests, and audit session and FastCGI settings where a fix has not yet shipped.

  • #php
  • #security
  • #cve
  • #php-fpm
  • #patching

Related posts