Tag: Nginx

  • PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 Security Update: What to Patch Now

    PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 Security Update: What to Patch Now

    Introduction

    This PHP security update, released on November 19, 2026, fixes 17 vulnerabilities in PHP 8.5, 8.4, 8.3 and 8.2, and seven of them are rated critical by the PHP project. The new PHP 8.6.0 released the same day contains the fixes too. PHP runs WordPress, Laravel, Symfony and a large share of managed hosting, so most PHP site owners should check their version this week.

    This article summarizes the official advisories, shows how to check your setup, and explains how to update, with no exploit steps. Our October 2026 PHP vulnerability update covers the previous round.

    Key Facts: PHP Security Update at a Glance

    • What: This PHP security update (8.5.13, 8.4.28, 8.3.37 and 8.2.36, released November 19, 2026) fixes 17 vulnerabilities.
    • Top issues: CVE-2026-129289 (PHP-FPM request smuggling), CVE-2026-129474 and CVE-2026-129182 (engine, PHP 8.5 only), CVE-2026-129496 (Date), and CVE-2026-129481, CVE-2026-126714 and CVE-2026-115560 (sessions).
    • Affected branches: PHP 8.5, 8.4, 8.3 and 8.2 before the fixed versions. Two advisories also list PHP 8.1.x ranges with no patched 8.1 version.
    • Fixed versions: 8.5.13, 8.4.28, 8.3.37, 8.2.36 (and 8.6.0).
    • Severity: Seven issues are rated critical (CVSS v4.0 score 9.2, assigned by the PHP project as CNA). NVD has not yet analyzed them.
    • Exploitation: No exploitation in the wild was reported in the advisories we reviewed. The CISA KEV catalog version we checked (2026.11.18) predates the disclosure.
    • Action: Upgrade to the fixed version for your branch, restart PHP-FPM and web server workers, and review the workarounds below if you cannot upgrade yet.

    PHP Security Update Overview: What Does It Fix?

    This PHP security update fixes 17 vulnerabilities across the PHP engine, PHP-FPM, sessions, Phar, SOAP, DOM and stream handling. The fixes are listed in the PHP 8 ChangeLog and in php-src GitHub security advisories, all published on November 19, 2026. The scores below are CVSS v4.0 base scores from the PHP project (security@php.net) as CVE Numbering Authority. The National Vulnerability Database (NVD) lists these CVEs as “Received” with only that score, so values may change.

    CVEComponentTypeCVSS v4 (PHP project)
    CVE-2026-129289PHP-FPMRequest smuggling through an unread request body, which can lead to code execution9.2 Critical
    CVE-2026-129474Engine (PHP 8.5 only)Use-after-free in magic method backtraces, remote code execution9.2 Critical
    CVE-2026-129182Engine (PHP 8.5 only)Use-after-free of the last fatal error backtrace after shutdown9.2 Critical
    CVE-2026-129496DateTimezone cache use-after-free, remote code execution9.2 Critical
    CVE-2026-129481Session (8.3 and later)Use-after-free after interrupted session shutdown9.2 Critical
    CVE-2026-126714Session (files handler)Partially overwritten session files can lead to remote code execution9.2 Critical
    CVE-2026-115560SessionSerializer mismatch can lead to remote code execution9.2 Critical
    CVE-2026-129291PHP-FPMEpoll use-after-free, local privilege escalation8.8 High
    CVE-2026-128064Standard (stream wrappers)Mixed-case HTTPS and FTPS URLs can expose data in plaintext8.2 High
    CVE-2026-127960Standard (HTTP wrapper)Denial of service through folded response headers8.7 High
    CVE-2026-128090PharOpenSSL signature bypass through algorithm downgrade7.7 High

    Six medium-rated fixes cover PHP-CGI, the PHP-FPM status page, SOAP, DOM and URI handling; see the php-src advisories linked below.

    Affected Versions: Which PHP Versions Are Affected?

    PHP 8.5, 8.4, 8.3 and 8.2 are affected until they reach 8.5.13, 8.4.28, 8.3.37 or 8.2.36. Individual CVEs affect different ranges, so check each advisory.

    PHP branchFixed inNotes from the advisories
    8.58.5.13Affected by all 17 issues, including the two 8.5-only engine bugs (CVE-2026-129474, CVE-2026-129182) and CVE-2026-129438
    8.48.4.28Affected by 14 of the issues, including CVE-2026-129501 (DOM, 8.4 and later)
    8.38.3.37Affected by 13 of the issues, including CVE-2026-129481 (session, 8.3 and later)
    8.28.2.36Affected by 12 of the issues; CVE-2026-129481 does not apply to 8.2
    8.1No fix listedTwo advisories list 8.1 ranges with no patched version: CVE-2026-129291 (8.1.20 to 8.1.34) and CVE-2026-127960 (8.1.32 to 8.1.34)

    Several advisories give the vulnerable range as “before 8.2.36” without a lower bound, so older, unsupported releases may also be affected. PHP 8.6.0 also contains the fixes, according to the changelog.

    Security Impact: What Can These Vulnerabilities Do?

    The worst-case impact is code execution as the PHP worker, but each critical issue needs specific conditions, which the advisories spell out.

    PHP-FPM request smuggling (CVE-2026-129289)

    If PHP does not read the whole request body, the leftover bytes can be interpreted as a second FastCGI request on a reused connection. According to the advisory, this can bypass front-end routing and run attacker-controlled PHP code as the worker, without memory corruption or a race. It needs a front end that keeps backend connections open, such as nginx with fastcgi_keep_conn on or Apache mod_proxy_fcgi with enablereuse=on, plus an application path that opens php://input without reading it fully. The nginx documentation lists fastcgi_keep_conn as off by default, and the advisory says configurations that close the connection after each request are not affected by the demonstrated attack.

    Memory-safety and session bugs

    The engine, Date and Session use-after-free bugs can crash a worker and, according to the advisories, could lead to code execution on affected setups. CVE-2026-129474 needs fatal_error_backtraces=1 and zend.exception_ignore_args=0; php.ini-production sets zend.exception_ignore_args=1, which blocks that path. CVE-2026-129496 needs a startup diagnostic and PHP error logging to a file. CVE-2026-126714 (default files handler) and CVE-2026-115560 (session upload progress) also require a suitable deserialization gadget chain in the application or its libraries.

    Data exposure and other issues

    CVE-2026-128064 can send data in plaintext when a stream function receives an HTTPS or FTPS URL with a mixed-case scheme, directly or through a redirect, exposing credentials, tokens or cookies to anyone who can observe the traffic. CVE-2026-129291 can raise a pool user to root if the FPM master runs as root and catch_workers_output is on, but the attacker first needs code execution in a worker. According to the advisory, the official PHP-FPM Docker images enable that option. CVE-2026-128090 only matters if you load OpenSSL-signed Phar archives.

    How Do I Check Whether the PHP Security Update Applies to Me?

    Check your PHP version first, then the few settings the advisories mention to see whether this PHP security update applies to you.

    How do I check my PHP version?

    Run these on each server and inside each container:

    php -v
    php-fpm -v

    Treat anything below 8.5.13, 8.4.28, 8.3.37 or 8.2.36 on its branch, and any 8.1 or older release, as affected. Linux distributions often backport fixes without changing the version number, so also check your vendor’s security tracker.

    How do I check the risky settings?

    The command-line php often reads a different configuration than PHP-FPM, so also confirm the FPM pool and web server settings:

    php -i | grep -E "fatal_error_backtraces|zend.exception_ignore_args|session.upload_progress.enabled|cgi.fix_pathinfo"
    php-fpm -tt 2>&1 | grep catch_workers_output
    nginx -T 2>/dev/null | grep -n fastcgi_keep_conn
    grep -rn "enablereuse" /etc/apache2 /etc/httpd 2>/dev/null

    If fastcgi_keep_conn on or enablereuse=on appears in front of PHP-FPM, treat CVE-2026-129289 as urgent. Also confirm that your Docker base images were rebuilt.

    How Do I Fix These PHP Vulnerabilities?

    Install the PHP security update by upgrading to PHP 8.5.13, 8.4.28, 8.3.37 or 8.2.36, then restart your PHP processes.

    How do I fix CVE-2026-129289 and the other issues?

    1. Back up first. See our guide on how to back up WordPress if you run a WordPress site.
    2. Upgrade to PHP 8.5.13, 8.4.28, 8.3.37 or 8.2.36 through your OS package manager, container base image or hosting panel. Source and Windows builds are on php.net.
    3. Restart PHP-FPM and web server workers and redeploy containers. Updated packages do not help until the running processes restart.
    4. Test your application, especially session upload progress, SOAP clients and Phar archives.
    5. Plan a move off PHP 8.1. The advisories list no patched 8.1 version for the two issues that affect it.

    What if I cannot upgrade right away?

    The advisories describe these temporary workarounds. They reduce exposure but are not complete fixes.

    IssueDocumented workaround
    CVE-2026-129289Keep fastcgi_keep_conn off in nginx and enablereuse off in Apache. Never expose PHP-FPM listeners to untrusted networks
    CVE-2026-129474Set zend.exception_ignore_args=1 or, on PHP 8.5, fatal_error_backtraces=0 for the FPM workers, then restart them
    CVE-2026-129496Fix startup warnings, restart PHP, or send PHP errors to syslog instead of a file
    CVE-2026-129291Disable catch_workers_output in affected pools
    CVE-2026-115560 / CVE-2026-126714Keep session.upload_progress.enabled=0 in every configuration that can write to the session store
    CVE-2026-129538Set cgi.fix_pathinfo=0 for php-cgi and test your routing
    CVE-2026-128064Lowercase URL schemes and validate every redirect target

    One more note from the CVE-2026-115560 advisory: if you explicitly enable session upload progress anywhere, every reader and writer of that session data must still use the same session.serialize_handler after updating.

    Additional Security Recommendations

    Applying the PHP security update is the main defense; these habits limit the damage from the next PHP bug.

    • Treat session data as untrusted input. Avoid unserialize() on user-influenced data and keep your dependencies current. Our OWASP Top 10 guide explains why this bug class keeps returning.
    • Use production error settings and isolate PHP-FPM. Start from php.ini-production, keep the FPM status page off the public internet, and use Unix sockets or private networks.
    • Do not rely on a firewall alone. A web application firewall does not replace patching.
    • Harden the host. Our Ubuntu server hardening guide covers automatic security updates.

    FAQ

    Is PHP 8.1 affected?

    Partly, and no 8.1 fix is listed. Two advisories list 8.1 ranges (CVE-2026-129291 for 8.1.20 to 8.1.34 and CVE-2026-127960 for 8.1.32 to 8.1.34) with no patched version. Several other advisories say “before 8.2.36” with no lower bound, so older releases may also be affected. Whether the PHP project will release an 8.1 fix is unknown.

    Is CVE-2026-129289 being exploited?

    No exploitation in the wild was reported in the advisories we reviewed, and the CISA KEV catalog version we checked (2026.11.18) predates the disclosure, so its silence is not proof. The advisory describes a demonstrated attack under specific configurations. Whether attackers are exploiting it now is unknown.

    Do I need to restart PHP-FPM after the PHP security update?

    Yes, restart PHP-FPM and your web server workers after installing the update so running processes use the fixed version. The advisories do not give a restart procedure; this is general practice.

    Does this affect WordPress sites?

    If your WordPress site runs on an affected PHP version, it uses the affected PHP runtime. The advisories we reviewed do not mention WordPress. The CVE-2026-129474 advisory names Laravel facades and Magento as code paths that reach the affected function, and says exploitation of a complete Laravel or Magento installation has not been demonstrated. Ask your host which PHP version you run.

    Conclusion

    The PHP security update is one upgrade per branch that closes all 17 vulnerabilities. Check your version, upgrade to 8.5.13, 8.4.28, 8.3.37 or 8.2.36, and restart PHP-FPM and your web server.

    References

    All links below returned HTTP 200 when checked on November 19, 2026.

    Related Articles

    Last Verified: November 19, 2026. Prepared by SafeWebAcademy from the official PHP project advisories and release notes linked above. This is not an official PHP project publication. Security details can change, so check the linked advisories for updates.