> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release7.2/security-advisories/php2shell-vulnerability-advisory.md).

# PHP2Shell Vulnerability Advisory

## Vulnerability Impact Assessment: PHP2Shell

<mark style="color:$warning;">CVE-2026-109618 | CVE-2026-109619</mark>

***

<table><thead><tr><th width="316.77783203125"></th><th></th></tr></thead><tbody><tr><td><strong>OvalEdge Status</strong></td><td><mark style="color:$success;"><strong>Not Impacted</strong></mark></td></tr><tr><td><strong>Customer Action Required</strong></td><td><strong>None</strong></td></tr><tr><td><strong>Published</strong></td><td>26 October 2026</td></tr><tr><td><strong>Issued By</strong></td><td>OvalEdge Security Center of Excellence</td></tr></tbody></table>

## Executive Summary

On 21 October 2026, the PHP project released emergency fixes for two critical remote code execution vulnerabilities in the PHP interpreter, tracked as **CVE-2026-109618** and **CVE-2026-109619**, and collectively referred to as "**PHP2Shell**".&#x20;

OvalEdge assessed its source code, dependencies, build artifacts, and repository container definitions for these vulnerabilities.

{% hint style="success" %}
**Conclusion:**&#x20;

**OvalEdge is not impacted by PHP2Shell.**

OvalEdge does not incorporate, bundle, compile, or execute PHP runtime environments in any of its offerings, including software products, build artifacts, container images, or managed infrastructure. No action is required from OvalEdge customers.
{% endhint %}

## Vulnerability Overview and Affected Technologies

<table data-header-hidden><thead><tr><th width="193.4443359375"></th><th></th></tr></thead><tbody><tr><td><mark style="color:$warning;"><strong>CVE-2026-109618</strong></mark></td><td>Remote code execution associated with memory corruption when PHP runs out of memory while processing an incoming request.</td></tr><tr><td><mark style="color:$warning;"><strong>CVE-2026-109619</strong></mark></td><td>Remote code execution associated with a PHP worker reusing stale state from an earlier request.</td></tr><tr><td><mark style="color:$primary;"><strong>Severity</strong></mark></td><td>Critical, CVSS v4.0 9.2 for each CVE</td></tr><tr><td><mark style="color:$primary;"><strong>Impact</strong></mark></td><td>Unauthenticated remote code execution on servers running a vulnerable PHP runtime that handles web requests.</td></tr><tr><td><mark style="color:$primary;"><strong>Affected Technology</strong></mark></td><td>PHP interpreter. Java, Python, JavaScript, and Apache Tomcat components are not directly affected unless they also include a vulnerable PHP runtime.</td></tr></tbody></table>

<table><thead><tr><th width="164.2222900390625">PHP Versions</th><th width="192.6666259765625">Affected Versions</th><th>Fixed Versions</th></tr></thead><tbody><tr><td>PHP 8.5</td><td>Before 8.5.12</td><td>8.5.12</td></tr><tr><td>PHP 8.4</td><td>Before 8.4.27</td><td>8.4.27</td></tr><tr><td>PHP 8.3</td><td>Before 8.3.36</td><td>8.3.36</td></tr><tr><td>PHP 8.2</td><td>Before 8.2.35</td><td>8.2.35</td></tr><tr><td>PHP 8.1 and older</td><td>Reported as affected</td><td>Vendor-patched packages or an upgrade to a supported version</td></tr></tbody></table>

## OvalEdge Impact Assessment

OvalEdge reviewed its source code, dependencies, build artifacts, and repository container definitions. No PHP runtime was identified in the reviewed scope.

<table><thead><tr><th width="218.6666259765625">Area</th><th width="371.7777099609375">Technology Stack</th><th>Status</th></tr></thead><tbody><tr><td><mark style="color:$primary;"><strong>OvalEdge platform</strong></mark></td><td>Java/Spring, JavaScript/React, Python/FastAPI, Apache NiFi</td><td><mark style="color:$success;"><strong>Not Impacted</strong></mark></td></tr><tr><td><mark style="color:$primary;"><strong>OvalEdge artifacts</strong></mark></td><td>Application WAR, Connector and JDBC libraries, container images</td><td><mark style="color:$success;"><strong>Not Impacted</strong></mark></td></tr><tr><td><mark style="color:$primary;"><strong>OvalEdge infrastructure</strong></mark></td><td>Linux, MySQL, Apache Tomcat, Elasticsearch</td><td><mark style="color:$success;"><strong>Not Impacted</strong></mark></td></tr><tr><td><mark style="color:$primary;"><strong>OvalEdge Bridge</strong></mark></td><td>Java, Apache NiFi</td><td><mark style="color:$success;"><strong>Not Impacted</strong></mark></td></tr></tbody></table>

## Recommended Actions

* **OvalEdge Deployments:** No patch, upgrade, or configuration change to OvalEdge is required for these vulnerabilities.
* **Customer-Managed Components:** Web servers, reverse proxies, and other software that customers operate alongside or in front of OvalEdge are outside the scope of this assessment. If any of these components run PHP, customers should update to a fixed PHP version listed in Section 2, following their vendor's security guidance.

Customers with questions about this advisory can contact OvalEdge Support.

## References

* PHP security advisory, CVE-2026-109618 (GHSA-w8hw-w9fx-j79w):\
  <https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w>
* PHP security advisory, CVE-2026-109619 (GHSA-6wmf-4rv5-p3rp):\
  <https://github.com/php/php-src/security/advisories/GHSA-6wmf-4rv5-p3rp>
* PHP release announcement:\
  <https://www.php.net/archive/2026.php#2026-10-21-1>

{% hint style="warning" %}
**Disclaimer:**

This advisory is provided for informational purposes and reflects OvalEdge’s assessment as of the publication date, based on information published by the PHP project and the security community at that time. OvalEdge will update this advisory if new information changes its conclusions.
{% endhint %}

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.


---

# 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.ovaledge.com/release7.2/security-advisories/php2shell-vulnerability-advisory.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.
