Executive Summary

CVE-2026-115560 abuses a mismatch between PHP session serializers, where attacker-controlled bytes stored via the session upload progress feature using the php_binary or php_serialize handler are later passed to the unserializer when the same session is read with the php serializer. In environments where human-machine interface portals, historian dashboards, or operator web consoles run PHP with shared session stores, this permits object injection and remote code execution on the host that mediates operator access to industrial processes.

Technical Exposure Breakdown

The vulnerable component is PHP session handling, specifically the interaction between the session upload progress mechanism and the serializer configured by session.serialize_handler. The attack vector is a remote attacker submitting a multipart file upload. When session upload progress is enabled, PHP writes progress data into a session key, and the attacker controls the name of that key. If the upload is handled while the php_binary or php_serialize handler is active, attacker bytes land inside a session value in a form the php serializer will later interpret as serialized object data.

Two conditions make this exploitable. First, the serializer must differ between the write and the read. This happens when session.serialize_handler is changed at runtime, or when two applications share a session store but are configured with different handlers. Second, the reading application must contain a usable gadget chain, meaning classes with magic methods such as __wakeup or __destruct that perform sensitive operations when an object is reconstructed. The groundwork is deserialization of untrusted data; the payoff depends on available gadgets.

Per the grounding data, this CVE was published on 2026-11-19. No CVSS score is provided, no affected version range is confirmed, and patch status is unknown. Treat all three as open until the upstream advisory lands. Do not assume a specific PHP branch is or is not affected based on this analysis.

OT Impact and Compliance Risk

PHP web stacks are common in the thin layer of OT that operators actually touch: configuration portals for RTUs and gateways, water utility customer and SCADA dashboards, pipeline reporting front ends, and vendor-shipped embedded web interfaces on industrial appliances. Code execution on one of these hosts gives an attacker a pivot point inside the control network perimeter, not merely a defaced web page. From that foothold an adversary can reach engineering workstations, poison historian data, or issue commands through the same application channels operators use.

Shared session stores are the specific risk multiplier here. Consolidated authentication portals or multi-tenant management applications that share a Redis, memcached, or filesystem session backend across apps with inconsistent serializer settings create the exact mismatch the CVE requires. The compliance exposure is direct. IEC 62443-3-3 requirements for application input validation and the SR 1.x identification and authentication controls are implicated by an authentication-adjacent portal executing attacker code. For electric utilities, NERC CIP-007 system security management and CIP-005 electronic security perimeter controls are affected if the vulnerable host sits in or borders a defined perimeter. For pipeline operators under TSA SD-02C and water systems under AWIA 2018, an internet-reachable PHP console that accepts uploads is a cyber incident reporting and remediation obligation.

Compensating Controls

Disable session upload progress where it is not required. Set session.upload_progress.enabled to off in the PHP configuration for any application that does not explicitly depend on it. This removes the attacker-controlled write primitive outright.

Enforce a single, consistent serializer across every application that shares a session store, and prohibit runtime changes to session.serialize_handler. Segment session backends so that unrelated applications do not share a store at all.

At the network layer, deploy inspection on the multipart upload path. A Suricata rule concept: inspect POST requests with Content-Type: multipart/form-data for form field names matching the upload progress prefix combined with serialized object markers such as O: or a: inside the body, and alert on that correlation. Rate-limit and authenticate all upload endpoints. Do not point an active vulnerability scanner at embedded industrial web interfaces to test this; aggressive upload probing and malformed multipart requests can hang or brick fragile device web stacks. Validate in a lab mirror first.

Do not wait on an upstream fix as your only control. BreachSpider's AI analysis flags the patch status for this CVE as unknown, so the compensating controls above are the operational priority.

BreachSpider Intel

BreachSpider tracks CVE-2026-115560 and related deserialization exposure across OT-adjacent web stacks; monitor the evolving advisory and KEV program status through BreachSpider.