RHSB-2026-020 Multiple vulnerabilities - PHP (CVE-2026-115560, CVE-2026-126714, CVE-2026-129182, CVE-2026-129289, CVE-2026-129474, CVE-2026-129496, CVE-2026-129481)

Created Date: November 19, 2026, 17:39
更新 November 19, 2026, 17:39

この情報は役に立ちましたか?

フィードバックがキャンセルされました

Ongoing 状態

Executive Summary

On November 19, 2026, the PHP project released security updates fixing several vulnerabilities across the PHP 8.2, 8.3, 8.4, and 8.5 branches. This bulletin covers the seven most severe of those flaws, most of which allow an unauthenticated remote attacker to execute arbitrary code with the privileges of the PHP worker. Red Hat is expediting the release of fixes.

  • CVE-2026-115560 — Critical — Session serializer mismatch can lead to remote code execution
  • CVE-2026-126714 — Critical — Partially overwritten session files can lead to remote code execution
  • CVE-2026-129289 — Critical — PHP-FPM request smuggling through an unread HTTP request body
  • CVE-2026-129496 — Critical — Timezone cache use-after-free can lead to remote code execution
  • CVE-2026-129481 — Important — Use-after-free after interrupted session shutdown

The following two flaws do not affect PHP versions shipped in Red Hat Enterprise Linux but are included here for awareness:

  • CVE-2026-129182 — Critical — Use-after-free via repopulation of fatal error backtrace after shutdown
  • CVE-2026-129474 — Critical — Use-after-free in magic method backtraces can lead to remote code execution

The investigation is ongoing and this bulletin will be updated as new information emerges. Log in with your Red Hat account, then click the "Follow" button below to be notified of changes to this bulletin.

Affected Products

The following Red Hat product versions are directly affected:

  • Red Hat Enterprise Linux 10
  • Red Hat Enterprise Linux 9
  • Red Hat Enterprise Linux 8
  • Red Hat Enterprise Linux 7

Further, any Red Hat product which is supported on Red Hat Enterprise Linux (including RHEL CoreOS) is also potentially impacted. This includes

  • Product containers that are based on the RHEL or UBI container images. These images are updated regularly, and container health indicating whether a fix to this flaw is available can be seen in the Container Health Index, part of the Red Hat Container Catalog. In addition, any customer containers should be rebuilt when the base images are updated.
  • Products that pull packages from the RHEL channel (this includes layered products such as Red Hat OpenShift Container Platform, Red Hat OpenStack Platform, Red Hat Virtualization, and others). Please ensure that the underlying RHEL php package is current in these product environments.

Mitigation

Overall Guidance

The configuration changes described below are temporary measures that reduce exposure until updates can be deployed, and should be removed once the updated packages are applied. All configuration changes require a restart of the PHP master process and all worker processes to take effect. The effective configuration must be verified for each PHP-FPM pool, virtual host, and application override; changing only the CLI configuration is insufficient.

Warning: Test these configuration changes in a non-production environment before deploying them. A restart of the PHP-FPM service briefly interrupts request handling and may have functional or performance side effects. Review each change against your own configuration, logging, and operational requirements before applying it.

Product-Specific Mitigation Steps

CVE-2026-129496 : Eliminate startup diagnostics and redirect error logging

This issue can be mitigated by correcting configuration errors and deprecated settings that produce diagnostics during PHP startup, then restarting the PHP master process and all workers. Alternatively, send PHP errors to a logging destination that does not use PHP's file-based error_log timestamp path, such as syslog:

error_log = syslog

Both measures remove the demonstrated trigger, which requires a startup diagnostic written through the file-based error log path followed by an early request diagnostic in a fresh worker. Changing $_REQUEST or cookie-related settings is not a complete mitigation.

CVE-2026-129289 : Disable FastCGI backend connection reuse

This issue can be mitigated by configuring the front end to close the backend connection after every request. Leave nginx fastcgi_keep_conn disabled (it is disabled by default), leave Apache mod_proxy_fcgi enablereuse disabled, and configure any other FastCGI front end, including HAProxy, to close retained backend connections. Standard nginx and Apache configurations
that close the FastCGI connection after each request are not affected by the demonstrated attack.

Reading php://input to completion in every request prevents the unread-body condition but is unreliable as the sole mitigation, because error paths and application shutdown can skip it. PHP-FPM and LSAPI listeners must not be exposed directly to untrusted networks.

CVE-2026-126714 and CVE-2026-115560 : Disable session upload progress

These issues can be mitigated by disabling session upload progress in every configuration that can write to the affected session store, for example in /etc/php.ini:

session.upload_progress.enabled=0

The setting must be applied administratively before request input is processed; calling ini_set() from the application is too late. The updated packages disable session upload progress by default, but an explicitly enabled setting overrides the new default.

For CVE-2026-115560, this removes the upload-progress attack path entirely. If the feature is required, every reader and writer of the session data must use the same session.serialize_handler, including across separate applications, PHP-FPM pools, virtual hosts, and command-line processes that share the session store, and session storage should be isolated between applications that require different formats.

For CVE-2026-126714, disabling upload progress removes that input path but does not address applications that independently store attacker-controlled data in sessions; the amount of untrusted data stored in sessions should also be limited. A session storage backend that replaces records atomically is not affected by the underlying file-write defect.

CVE-2026-129481 : Prevent worker reuse across session cleanup failures

This issue can be mitigated by avoiding fatal errors in callbacks reached during session cleanup, such as user-defined stream wrappers whose stream_close() method can abort session shutdown.

For PHP-FPM, limiting each worker to a single request prevents the demonstrated two-request sequence from reaching the same worker, at a
significant performance cost. Set this in the relevant pool file under /etc/php-fpm.d/ (for example /etc/php-fpm.d/www.conf):

pm.max_requests=1

CVE-2026-129474 and CVE-2026-129182 : Disable fatal error backtraces

Note: These two flaws affect PHP 8.5 only. Red Hat Enterprise Linux does not ship PHP 8.5 and are not affected; deployments running PHP 8.5 are affected.

These issues can be mitigated by disabling fatal error backtraces in the configuration used by the affected PHP workers, either in /etc/php.ini or in the relevant PHP-FPM pool file under /etc/php-fpm.d/:

fatal_error_backtraces=0
zend.exception_ignore_args=1

Then restart the PHP-FPM service:

systemctl restart php-fpm.service

Setting zend.exception_ignore_args=1 additionally blocks the demonstrated attack path for CVE-2026-129474 independently of the backtrace setting. Ensure that request-specific configuration cannot re-enable either setting.
Note that setting display_errors=0 does not prevent PHP from constructing the backtrace and is not a mitigation.

References

PHP upstream advisory for CVE-2026-115560

PHP upstream advisory for CVE-2026-126714

PHP upstream advisory for CVE-2026-129182

PHP upstream advisory for CVE-2026-129289

PHP upstream advisory for CVE-2026-129474

PHP upstream advisory for CVE-2026-129496

PHP upstream advisory for CVE-2026-129481

How to use GPG to verify signed content from Product Security

この情報はお役に立ちましたか? お客様のフィードバックをお待ちしております。

フィードバックがキャンセルされました

Comments