SAASMENT

News

PHP scheduled critical fixes for every supported version.

PHP set a security release for 19 November 2026, between 14:00 and 14:30 UTC, covering flaws in every supported version, and that release is expected to include a remote code execution bug that works only when an app switches its session serializer in a specific way while session upload progress stays on.

Illustration of a progress bar cracking open a server while session blocks scatter

Impact

What was impacted
Every supported PHP version, in a security release scheduled for 19 November 2026 between 14:00 and 14:30 UTC. PHP said the releases are part of its regular four-week cycle, the highest severity is critical, and critical issues need a non-default configuration or an uncommon setup. It did not describe each flaw. The release is expected to include CVE-2026-115560, remote code execution that succeeds only when an application sets session.serialize_handler to php_binary or php_serialize and then switches that handler to php with ini_set() before session_start(), and session upload progress is enabled. Session upload progress is on by default.
Who was impacted
Operators of supported PHP versions, especially applications that change session.serialize_handler at runtime in that way. The advisory did not list the supported version numbers. Separate, already patched bugs in the same report matter if those fixes are still missing: CVE-2026-109618 and CVE-2026-109619 (PHP2Shell) have seen limited exploitation against publicly reachable Palo Alto Networks management interfaces and Check Point Security Gateways.
What you need to do
Install the 19 November 2026 security releases as soon as they are published. For CVE-2026-115560, set session.upload_progress.enabled=0 and restart the PHP worker; that is the mitigation advised until the next regular bugfix release. Also confirm the already published fixes for CVE-2026-109618, CVE-2026-109619, and the Brotli decoder flaw CVE-2026-111497 are installed. The advisory did not name package versions.

PHP issued an advisory for a security release on 19 November 2026, between 14:00 and 14:30 UTC. The maintainers said the releases are part of the regular four-week cycle and will address vulnerabilities in every supported PHP version. They rated the most serious issues critical, and said those critical issues need either a non-default configuration or an uncommon setup. They did not describe the flaws beyond that.

The release is expected to include CVE-2026-115560. That remote code execution bug succeeds only when two conditions are both true. The application sets session.serialize_handler to php_binary or php_serialize, and its code switches the handler to php with ini_set() before session_start(). Session upload progress must also be enabled. That second setting is PHP’s default, so the unusual part is the serializer switch.

Until the next regular bugfix release, set session.upload_progress.enabled to 0 and restart the PHP worker. The restart is required for the setting to apply. Install the security updates as soon as they are published. The advisory did not name the new version numbers.

About a month earlier, PHP shipped fixes for CVE-2026-109618 and CVE-2026-109619, tracked together as PHP2Shell. Those bugs allow unauthenticated remote code execution through crafted HTTP requests, and they have seen limited active exploitation. The activity named in the report targeted publicly reachable Palo Alto Networks management interfaces and Check Point Security Gateways, then moved on to Active Directory and backdoors. On 30 October 2026, Hunt.io said it had found 616 PHP2Shell-related files across hosts, including shared exploit kits, cloned proofs of concept, custom heap exploits, scanners, and post-exploitation tools. CrowdStrike said developers are unlikely to produce one exploit that works reliably on every affected PHP deployment.

Last month PHP also patched CVE-2026-111497, a critical out-of-bounds write in the Brotli decoder library, also called Node2Shell or Broccoli2Shell, that can lead to code execution. Apply that update if it is not already in place, along with the November security releases when they ship.

For your AI agent

Agent instructions — copy paste to Claude

You are helping me respond to PHP’s security advisory for releases scheduled on 19 November 2026 between 14:00 and 14:30 UTC. PHP said these releases are part of the regular four-week cycle and will address vulnerabilities in every supported PHP version. The highest severity is critical. PHP said critical issues need a non-default configuration or an uncommon setup, and it did not describe every flaw.

The release is expected to include CVE-2026-115560, remote code execution that succeeds only when both of these are true:
- The application sets session.serialize_handler to php_binary or php_serialize, and its code switches the handler to php with ini_set() before session_start().
- Session upload progress is enabled. That setting is PHP’s default.

Mitigation advised until the next regular bugfix release: set session.upload_progress.enabled=0 and restart the PHP worker so the setting applies.

Related issues in the same report that already have published fixes:
- CVE-2026-109618 and CVE-2026-109619 (PHP2Shell), patched about a month earlier: unauthenticated remote code execution through crafted HTTP requests. Limited active exploitation has targeted publicly reachable Palo Alto Networks management interfaces and Check Point Security Gateways, with follow-on activity against Active Directory and backdoors. Hunt.io said on 30 October 2026 that it found 616 related files across hosts, covering exploit kits, cloned proofs of concept, heap exploits, scanners, and post-exploitation tools. CrowdStrike said one exploit that works reliably on every affected PHP deployment is unlikely.
- CVE-2026-111497, a Brotli decoder out-of-bounds write also called Node2Shell or Broccoli2Shell, patched last month. It can lead to code execution.

Context:
- What was impacted: every supported PHP version in the scheduled security release, and session handling when the CVE-2026-115560 conditions are met. Supported version numbers were not listed.
- Who should care: operators of supported PHP, especially apps that change session.serialize_handler at runtime as described. Teams still missing the PHP2Shell fixes, including those running the named Palo Alto management interfaces or Check Point Security Gateways, should confirm those earlier patches too.
- What to do: install the security releases when they are published, apply the upload-progress mitigation until the next regular bugfix release, and confirm the earlier PHP2Shell and Brotli fixes are already installed.

Do this in order. Ask before editing php.ini, pool configs, or restarting PHP workers. Prefer read-only inventory first. Do not write or run an exploit, a proof of concept, or a crafted request meant to trigger these bugs.

1. Inventory
   - Record the PHP version and whether it is still on a supported branch. The advisory did not list version numbers, so do not guess them.
   - Search configuration and code for session.serialize_handler set to php_binary or php_serialize, and for ini_set that switches the handler to php before session_start().
   - Record the effective value of session.upload_progress.enabled. The default is on.
   - Note whether the 19 November 2026 security builds are already installed, and whether fixes for CVE-2026-109618, CVE-2026-109619, and CVE-2026-111497 are present. If the package advisory is not in front of you, say so instead of inventing a version.
2. Contain
   - If the CVE-2026-115560 conditions match, or you cannot show that they do not, propose session.upload_progress.enabled=0 and a PHP worker restart. Ask before applying it. That mitigation was advised until the next regular bugfix release.
3. Remediate
   - When the 19 November 2026 security releases are available, plan the upgrade and ask before restarting workers.
   - If the PHP2Shell fixes or the Brotli decoder fix are missing, plan those already published updates as well. Ask before installing.
4. Verify
   - Confirm the running PHP binary or package is the build you intended, and that session.upload_progress.enabled is 0 on any host still waiting on the next regular bugfix release.
5. Report back
   - Versions found, whether the session-handler switch is present, the upload-progress setting, what was upgraded or mitigated, and anything still unpatched.

Do not invent CVEs, package versions, or exploit conditions. If a check needs access I have not given you, say what you need and stop.

← All news

Try the platform.

Open the demo workspace with mock data. No login. Register from the banner when you want early access. No security team. No call.

Try the platform