Skip to content
eastbaycyber

PHP releases security updates for supported versions

Breaking news 7 min read
EC
East Bay Cyber Editorial Team Updated Developing story
Built from the vendor or authority notice plus independent reporting; unconfirmed claims are labeled as reported. Human-reviewed after publishing.

CVE explainers: CVE-2026-109618, CVE-2026-109619

TL;DR - Update: PHP has published the scheduled security releases, including PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36, and has released PHP 8.6.0. - PHP says CVE-2026-115560 requires an unusual combination of session configuration and application code. - PHP recommends setting session.upload_progress.enabled=0 until the next regular bugfix release, but says an update is the complete solution. - Earlier PHP2Shell vulnerabilities, CVE-2026-109618 and CVE-2026-109619, were fixed in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. - Hunt.io reported exploit tooling and shell activity, while other researchers reported failed attempts or no observed exploitation.

What happened#

PHP has published the security releases previously scheduled for Thursday, 19 November 2026. The PHP news archive lists PHP 8.5.13, PHP 8.4.28, PHP 8.3.37 and PHP 8.2.36 as security releases, and says users on each branch are encouraged to upgrade. The same archive announces the immediate availability of PHP 8.6.0, a major update to the PHP language. PHP

The archive says the scheduled releases address vulnerabilities affecting all supported PHP versions. It previously identified the highest severity as CRITICAL, while noting that issues rated CRITICAL require either non-default configuration or uncommon setups.

PHP has now published additional information about CVE-2026-115560. The issue can occur when an application sets session.serialize_handler to php_binary or php_serialize, changes it to php at runtime with ini_set() before calling session_start(), and leaves session upload progress enabled. PHP says applications that never change the serialize handler at runtime can keep the feature enabled.

The PHP archive recommends setting session.upload_progress.enabled=0 until the next regular bugfix release. It says this issue is unlikely in practice and will be handled in the regular release cycle. The archive also says a full advisory for CVE-2026-115560 will be published with the next release.

The archive separately records earlier fixes for CVE-2026-109618 and CVE-2026-109619. PHP describes those as two critical vulnerabilities that can allow unauthenticated remote code execution, fixed in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. It identifies PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed as affected PHP installations serving web requests.

Are you affected#

Organizations should review any deployment running a PHP version covered by the PHP security releases. The current fixed versions listed by PHP are PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 for the newly published security releases.

The PHP archive says PHP 8.1 and older no longer receive updates from the PHP project. It adds that some distributions and LTS vendors provide backported fixes, and recommends contacting the relevant vendor or upgrading to a supported version.

CVE-2026-115560 has specific configuration and application-code requirements. The application must set session.serialize_handler to php_binary or php_serialize, switch it to php at runtime with ini_set() before session_start(), and have session upload progress enabled. PHP says the issue can occur only under this unusual combination.

Teams should also determine whether earlier PHP2Shell fixes are installed. PHP lists PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 as fixing CVE-2026-109618 and CVE-2026-109619. Linux distributions and LTS vendors received those patches in advance, so package versions may differ from the upstream PHP versions.

Exploitation reporting is mixed. Hunt.io reported shells on honeypots and sensors and identified 616 PHP2Shell-related files, while also stating that it found no evidence of reliable mass compromise on the open internet. Hunt.io reported confirmed production compromises against PAN-OS, rather than reliable compromise of arbitrary PHP deployments. Hunt.io The Hacker News reported limited active exploitation targeting publicly accessible Palo Alto Networks management interfaces and Check Point Security Gateways, but PHP’s archive does not state that CVE-2026-115560 is being exploited. The Hacker News

What is confirmed and what is reported#

Claim Source Status
PHP 8.5.13 is an immediately available security release. PHP Confirmed
PHP 8.4.28 is an immediately available security release. PHP Confirmed
PHP 8.3.37 is an immediately available security release. PHP Confirmed
PHP 8.2.36 is an immediately available security release. PHP Confirmed
PHP 8.6.0 is immediately available. PHP Confirmed
CVE-2026-115560 requires session.serialize_handler to be set to php_binary or php_serialize, changed to php at runtime with ini_set() before session_start(), while session upload progress remains enabled. PHP Confirmed
PHP recommends setting session.upload_progress.enabled=0 until the next regular bugfix release. PHP Confirmed
CVE-2026-109618 and CVE-2026-109619 were fixed in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP Confirmed
CVE-2026-109618 and CVE-2026-109619 enable unauthenticated remote code execution. PHP Confirmed
Hunt.io identified 616 PHP2Shell-related files. Hunt.io Reported
Hunt.io observed shells on honeypots and sensors, but no reliable mass compromise on the open internet. Hunt.io Reported
The Hacker News reported limited active exploitation targeting Palo Alto Networks management interfaces and Check Point Security Gateways. The Hacker News Reported
The Hacker News reported that CVE-2026-115560 is a remote code execution flaw under the stated configuration conditions. The Hacker News Reported

PHP has confirmed the available versions, the conditions for CVE-2026-115560, and the mitigation guidance. Reporting about exploitation of the earlier PHP2Shell vulnerabilities comes from Hunt.io and The Hacker News. The PHP archive does not state that CVE-2026-115560 is being exploited.

What defenders should do now#

  1. Inventory PHP installations, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed deployments. Record the installed version, package vendor, operating system and internet-facing applications.

  2. Upgrade supported upstream installations to the applicable PHP security release: PHP 8.5.13, 8.4.28, 8.3.37 or 8.2.36. PHP identifies these as security releases and encourages users on those branches to upgrade.

  3. Check Linux distribution and LTS vendor channels for corresponding packages. PHP says those vendors received patches in advance for the earlier vulnerabilities, and their package versions may differ from the upstream PHP version numbers.

  4. Review application code and configuration for CVE-2026-115560. Look for session.serialize_handler set to php_binary or php_serialize, a runtime switch to php using ini_set(), a subsequent session_start(), and enabled session upload progress.

  5. If the applicable PHP update cannot be deployed immediately, follow PHP’s interim guidance by setting session.upload_progress.enabled=0. PHP describes this as a mitigation until the next regular bugfix release, not as a complete substitute for updating.

  6. Confirm that PHP workers receive the changed configuration. The Hacker News reported that restarting the PHP worker was recommended for the setting to apply, while PHP’s archive says the mitigation should remain in place until the next regular bugfix release.

  7. Check whether systems still run PHP 8.1 or older. PHP says those versions no longer receive project updates, although some distributions and LTS vendors provide backported fixes.

  8. Review exposure to CVE-2026-109618 and CVE-2026-109619 separately. PHP says those vulnerabilities affect PHP installations serving web requests and were fixed in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35.

  9. Review relevant web, PHP worker and endpoint telemetry for unexpected shell creation or suspicious requests, while treating third-party exploitation reports as context rather than proof that a particular environment was compromised.

This advisory is informational and is updated as vendors publish details. Confirm versions and actions against PHP and the relevant package vendor guidance for your environment.

This advisory is informational and is updated as vendors publish details. Confirm versions and actions against the vendor’s own guidance for your environment.

Sources

Last verified: 2026-11-20

Disclaimer: This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.