Bastion Cyber Threat Brief | October 23, 2026: Critical PHP RCE Fixes Prompt Cisco Product Review

Executive takeaway
On October 21, the PHP project published fixes for CVE-2026-109618 and CVE-2026-109619, two critical flaws whose advisories describe confirmed unauthenticated remote code execution under specific server and application conditions. Organizations that operate PHP directly—or depend on products that embed it—should identify exposed versions and move to fixed releases. PHP advisories
On October 22, Cisco updated an interim product advisory that lists Ultra-Reliable Wireless Backhaul and the Expressway and Expressway Select series as affected, while several other products and cloud services remain under investigation. Cisco says it is not aware of malicious use of these vulnerabilities. Cisco advisory
What happened and when
Both PHP advisories list releases earlier than 8.2.35, 8.3.36, 8.4.27 and 8.5.12 as affected, and identify those four versions as patched. CVE-2026-109618 concerns out-of-memory corruption; CVE-2026-109619 concerns stale global state retained across requests. The advisories document remote-code-execution impact under defined conditions, but the applicable path and reliability depend on the PHP server interface, configuration and application behavior. CVE-2026-109618 advisory
Cisco first published its advisory on October 21 at 19:12 GMT and last updated it on October 22 at 23:00 GMT. Version 1.4 revised the lists of products under investigation and products confirmed not vulnerable. The advisory remains interim, and fixed-release availability varies by affected product. Cisco revision history and product status
Who should pay attention
Bastion analysis: This is relevant to teams responsible for web applications, APIs, content-management and commerce platforms, managed hosting, and vendor products that may include PHP. Exposure cannot be determined from a product category alone; the effective runtime version and deployment path have to be checked.
Why a business should care
Bastion analysis: A widely used runtime can create two separate remediation questions—where your organization runs PHP itself, and which third-party products carry it as an embedded dependency. SaaS firms and growing businesses should assign ownership for both application updates and vendor follow-up so an under-investigation product does not disappear between infrastructure and procurement teams.
Practical defensive next steps
Inventory the PHP versions actually running in production, development, container images and managed platforms. Move each maintained branch to its fixed release: 8.2.35, 8.3.36, 8.4.27 or 8.5.12. Then validate the effective runtime version and restart worker pools where the deployment requires it. PHP fixed versions
If an immediate update is not possible, read both PHP advisories before applying temporary configuration measures. The maintainers state that updating is the only complete or reliable mitigation; configuration changes do not cover every path. Related PHP mitigation guidance
For Cisco products, compare each deployment with the latest vendor table, track items still under investigation, and use Cisco TAC or a contracted support provider when the release path is unclear. Cisco says there are no workarounds that address these vulnerabilities. Cisco product guidance
Limits and dates
The PHP advisories establish technical exploitability; they do not establish a confirmed in-the-wild campaign. Cisco says it is not aware of malicious use. A product listed as under investigation is not yet confirmed affected, and this brief is not evidence that any reader has been compromised. Cisco exploitation statement
Original PHP disclosures: October 21, 2026; no release time shown. Cisco advisory first published October 21, 2026, 19:12 GMT; last updated October 22, 2026, 23:00 GMT. Verified as of October 23, 2026, 8:30 a.m. Eastern.

Comments