PHP2Shell (CVE-2026-109618 and CVE-2026-109619)
| Period | 20 October 2026, evening, to 22 October 2026 |
| Affected services | PHP applications on the Cloudbear Automation Platform (CAP), Managed CloudPanel servers, Managed DirectAdmin servers (including Webbear), and Cloudbear's own PHP tools |
| Severity | Critical (CVSS v4 9.2, remote code execution) |
| Status page | status.cloudbear.nl, incident 253 |
| Report date | 22 October 2026 |
All times are in CEST (GMT+2), the time zone that we used in our messages to you.
1. Summary
On the evening of 20 October 2026, details of two critical vulnerabilities in PHP became public. The vulnerabilities let an attacker run code on a server with one crafted HTTP request. All supported PHP versions were affected. The PHP project announced an emergency release for 21 October, 16:00.
We informed all customers at 09:05 on 21 October and applied a temporary mitigation. At 12:31 we advised you to take your PHP applications offline until the fix was available. This followed the advice of CERT-EU. We took our own PHP systems offline between 12:28 and 12:54. Most customers chose to go offline.
The PHP project published the fixed versions at approximately 15:40. We did not wait for all vendors. We built patched PHP and FrankenPHP images ourselves. The Managed CloudPanel servers were back online at 17:10, and the first CAP applications at 17:15. All important production environments were back online at 19:33. The last servers received the vendor fix in the night of 22 October.
We found no sign that an attacker used the vulnerabilities on the applications that we checked. Section 6 explains what we checked and the limits of that check.
2. The vulnerabilities
- CVE-2026-109618: a crafted multipart request makes PHP run out of memory while it reads the request. Browsers use the multipart format for file uploads and forms. This occurs before the application code starts. The application does not have to accept uploads.
- CVE-2026-109619: after such a failure, a later request on the same PHP worker can use data that the failed request left behind.
- Fixed versions: PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12.
- Older versions: the PHP project published no releases for PHP 7.4, 8.0 and 8.1. It published minimal source backports for these versions instead. You must build PHP yourself to use them, or get a package from an LTS vendor.
- Advisories: GHSA-w8hw-w9fx-j79w, GHSA-6wmf-4rv5-p3rp, and CERT-EU advisory 2026-018.
Only the PHP update fixes both vulnerabilities. The temporary mitigation that we applied in the morning (session.upload_progress off) blocks one known attack path of CVE-2026-109619. It does not stop CVE-2026-109618.
3. Timeline
20 October
| Time | Event |
|---|---|
| Evening | Details of the vulnerabilities become public. The PHP project announces an emergency release for 21 October. |
| Late evening | Cloudbear receives the notification and makes the PHP fix the first priority for the next day. |
21 October
| Time | Event |
|---|---|
| Morning | The team starts the emergency response. We postpone the planned Kubernetes upgrades of that day. |
| 09:05 | First message to all customers. We announce the temporary mitigation and the PHP upgrade that follows. |
| 09:25 – 10:38 | We set up our own pull-through cache for PECL, so our image builds depend less on the public PECL service. The cache works for some of our image builds, but not for all. |
| 09:55 – 10:50 | The temporary mitigation is live on all CAP apps, Managed CloudPanel servers and Managed DirectAdmin servers. |
| Late morning | Reports of a working exploit appear. CERT-EU advises to take internet-facing PHP applications off public networks until they are patched. |
| 12:28 – 12:32 | We take the Webbear website offline. We announce that CAP and our own PHP tools go offline. |
| 12:31 | We advise all customers to take their PHP applications offline. Each customer can choose one of four options per application. The options are: keep online, block file uploads, turn off at 16:00, or turn off now (our advice). |
| 12:54 | CAP goes offline. Applications keep running, but deployments are not possible. |
| 13:21 – 14:53 | We take customer applications offline on request. Only web traffic stops. Workers and scheduled jobs keep running. |
| 13:35 – 13:38 | Managed CloudPanel servers go offline, including the control panel. |
| 14:09 | Update to customers: please check that your application is really offline. |
| 14:15 – 15:02 | PHP is switched off on the Managed DirectAdmin servers. Static HTML pages stay online. |
| 14:58 | We announce the rollout plan: first CAP, then the applications. Customers must not deploy until we give permission. |
| ~15:40 | The PHP project publishes the fixed versions. |
| 15:56 | Update to customers: the fix is out, and we wait for the vendor packages. |
| 16:35 | The official FrankenPHP release was not available yet, so we built our own patched PHP and FrankenPHP base images. They were ready at this moment. |
| 17:05 – 17:10 | Managed CloudPanel servers are back online with an interim protection extension. |
| 17:15 – 17:31 | The first CAP applications are back online on the patched PHP version. |
| 17:27 | Managed DirectAdmin servers are back online behind a web application firewall rule. |
| 17:46 – 19:12 | Most CAP applications are back online on the patched PHP version. |
| 17:53 | CAP is back online on the patched PHP version. |
| 18:37 – 19:38 | Managed CloudPanel servers receive the vendor packages for PHP 8.2 to 8.5. |
| 19:33 | Update to customers: all important environments are restored. |
| 20:37 – 21:52 | The last CAP applications are back online. A cleanup policy in the customer's own registry had removed their old images, so we had to restore them first. Most of these applications were not yet critical for the customer. |
| 22:04 | Check of all running CAP containers: all customer containers use the patched PHP version. |
| 22:18 | End-of-day message to customers. A safeguard now blocks deployments of images with an unpatched PHP version. We ask customers to coordinate their first deployment with us. |
22 October
| Time | Event |
|---|---|
| 00:13 – 00:26 | Managed CloudPanel servers receive patched builds of PHP 7.4 and 8.1 from a third-party repository. CloudPanel supplies no fix for these versions. |
| 00:29 | CloudLinux publishes the patched PHP packages for DirectAdmin servers. |
| 00:49 – 01:44 | All Managed DirectAdmin servers receive the CloudLinux packages for PHP 5.2 to 8.5. |
| Afternoon | The Webbear website is back online on a new version. |
4. What we did per platform
Cloudbear Automation Platform (CAP)
A normal PHP update goes through your own release pipeline. That takes time, and your release schedule controls it. To move faster, we replaced only the PHP base layers in the images that were already running. Your application code did not change. Each image took approximately 15 seconds.
- We built patched base images ourselves for PHP 8.2, 8.3, 8.4 and 8.5.
- We replaced the base layers in each running application image.
- We checked each running container for the patched PHP version, both on the command line and in the web server.
No CAP application used PHP 8.1 or older.
Your next normal release builds on the patched base images. A safeguard blocks deployments of images with an unpatched PHP version.
Managed CloudPanel servers
- An interim protection extension blocks the known attack patterns. It is active for PHP 7.1 to 8.5.
- PHP 8.2 to 8.5 have the CloudPanel vendor packages.
- PHP 7.4 and 8.1 have patched builds from a third-party repository, because CloudPanel gives no fix for them.
- Unused older PHP versions are stopped.
- Next step: we make a list of the sites that use PHP 7.4 or 8.1. We do not consider these versions safe. We will contact each of these customers to agree on a timeline for the upgrade.
Managed DirectAdmin servers (including Webbear)
- A web application firewall rule from CloudLinux (Imunify360) blocked the known attack patterns from the afternoon of 21 October.
- CloudLinux published patched packages at 00:29 on 22 October. They are installed for PHP 5.2 to 8.5.
- PHP 4.4 and 5.1 get no fix.
- Next step: we will contact the customers whose sites use a PHP version that CloudLinux does not update. We will agree on a timeline for the upgrade, and then disable these versions.
Cloudbear's own services
- CAP, our billing tools and the support desks run the patched PHP version.
- The Webbear website was offline until we had a new version. It came back online on 22 October.
5. Cause
The cause is two vulnerabilities in PHP itself. Cloudbear and our customers did not cause them.
The risk was high for three reasons:
- The details became public before the fix was available.
- An attacker needs no account and no specific application feature. One request to any PHP page is sufficient.
- Reports of working exploits appeared in the late morning of 21 October.
6. Did an attacker use the vulnerabilities?
We examined the logs of the CAP applications from the evening of 20 October, 23:00, to the moment that the applications went offline.
- We found no sign of an attack on these applications.
- PHP logged no out-of-memory errors of the type that this attack causes.
- Automated scanners sent requests to our platform. None of them got a successful response from a PHP application.
Limits of this check: web servers do not log the content of requests, so we cannot search for the attack itself. We looked for side effects, such as crashes and unusual request patterns. A clean result lowers the risk, but it does not prove that no attack occurred.
7. Evaluation
What went well
- We informed all customers at 09:05 on the first morning, and we stayed available for questions during the whole day.
- We advised to go offline before the fix was out. Most customers chose that option, so most applications were offline during the period of highest risk.
- We made an ad-hoc rollout procedure for CAP on the morning of 21 October, before the fix was published. We tested it on all application registries before 16:00.
- We did not wait for vendors. We built patched images ourselves, and most applications were back online within approximately 4 hours after the PHP release.
- We checked each patched application for the patched PHP version in the running web server.
What needs improvement
- Our mitigation message was too positive. We said that the mitigation would "hopefully" close one of the two vulnerabilities. The official advisories showed later that it blocks only one attack path of CVE-2026-109619. It does not stop CVE-2026-109618.
- Some images were missing. Some customers use a cleanup policy in their own registry. This policy had removed the images of some running applications, because nobody had updated these applications for a long time. Most of them ran in a production environment, but they were not yet critical for the customer. Our test before 16:00 checked that we could push new images to each registry. It did not check that the old images were still present. We had to rebuild or recover these images, which delayed their return by several hours.
- Vendor packages were incomplete. Some vendor packages missed extensions or arrived hours after the vendor announcement. We had to check each package before we used it.
- PECL and other package registries had problems. Our image builds download PHP extensions from PECL. During our preparation, PECL was not reliable. On the morning of 21 October, between 09:25 and 10:38, we set up our own pull-through cache for PECL. The cache worked for some of our image builds, but not for all. Fortunately, this did not delay the rollout much.
- No general procedure for this scenario. We have procedures for many scenarios. We had no general procedure to patch a large number of containers at the same time. The procedure of 21 October was built before the release of the fix. In general, it worked well after the release (except for Some images were missing).
8. Our advice: update to PHP 8.5
We advise all customers to update their applications to PHP 8.5. The patches of this incident close these two vulnerabilities, but they do not make older PHP versions safe for the future.
- CAP: update the PHP version in your application. Change your Dockerfile so that it uses the base container for that PHP version. Then do a normal release.
- Managed DirectAdmin servers: select PHP 8.5 for your websites. We will contact you if your sites use a PHP version that CloudLinux does not update. We do not consider these versions safe, and we will agree on a timeline for the upgrade with you. After that, we will disable these versions.
- Managed CloudPanel servers: we will contact you if your sites use PHP 7.4 or 8.1. We do not consider these versions safe, and we will agree on a timeline for the upgrade with you.
If you need help with the upgrade, contact us.
9. Action items
| # | Action |
|---|---|
| 1 | Make sure that a registry cleanup never removes an image that CAP uses. We will move the images to our own registry. CAP will manage the cleanup policy of that registry. |
| 2 | Write a procedure for an emergency container update on CAP-managed apps. Use local caches as much as possible. |
| 3 | Advise all customers to update their applications to PHP 8.5. |
| 4 | Contact customers running Managed CloudPanel servers with PHP 7.4 or 8.1. Then disable these versions. |
| 5 | Contact customers running Managed DirectAdmin servers that use a PHP version that CloudLinux does not update. Then disable these versions. |
Questions
If you have a question about this report or about your applications, contact us in your Slack channel or through support.