> For the complete documentation index, see [llms.txt](https://docs.cloudbrink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudbrink.com/security-advisory/cbsa-2026-oct-001-php2shell-vulnerabilities.md).

# CBSA-2026-OCT-001: PHP2Shell Vulnerabilities

{% hint style="success" %}
**Status: Not Affected** · Severity: Informational
{% endhint %}

### Document revision history

| S.No | Revision, Date       | Description            | Status, Severity            |
| ---- | -------------------- | ---------------------- | --------------------------- |
| 1    | 1.0, 23 October 2026 | Initial public release | Not Affected, Informational |

### Subject

PHP2Shell Vulnerabilities (CVE-2026-109618, CVE-2026-109619)

### Summary

On 21 October 2026, the PHP project released security updates for two critical vulnerabilities in the PHP interpreter, publicly referred to as "PHP2Shell":

* **CVE-2026-109618** (CVSS v4.0: 9.2): Remote code execution via out-of-memory corruption (GHSA-w8hw-w9fx-j79w)
* **CVE-2026-109619** (CVSS v4.0: 9.2): Remote code execution via stale global state (GHSA-6wmf-4rv5-p3rp)

Both vulnerabilities affect PHP versions 5.4 through 8.5.11 and can allow an unauthenticated attacker to execute code remotely.

### Impact on Cloudbrink

We have reviewed the Cloudbrink platform, including the cloud service, management console, partner portal, connectors, edges, and endpoint agents. None of these components use PHP, and they are not affected by CVE-2026-109618 or CVE-2026-109619.

### What customers should do

No action is required by customers on Cloudbrink components.

We continue to monitor this issue and will notify you if our assessment changes. For any questions, contact <support@cloudbrink.com>.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cloudbrink.com/security-advisory/cbsa-2026-oct-001-php2shell-vulnerabilities.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
