Status in the company's own words: patching. Statement dated Resolved Oct 22, 2026 06:36 EDT; Recovering Oct 22, 2026 05:17 EDT.
This index reports published statements and AI answers on stated dates. It is not a security assessment. For patching, follow PHP's advisory and your host.
Patches from upstream vendors have been released and are currently being deployed across the fleet in rolling waves. quoted from https://status.rocket.net/incident/3178 (title: PHP Update). Incident marked Resolved at Oct 22, 2026 06:36 EDT with a thank-you note only; no update states deployment finished, so recorded as patching. Patches apply to PHP 5.2 through 8.5; customers advised to move to PHP 8.2 or later via Mission Control; Cloudflare Enterprise WAF named as an extra layer.
Change log
: first check
What the five engines said
ChatGPT
match
Captured . Status named: patching. Cites a rocket.net page.
Rocket.net’s PHP hosting was in scope, and Rocket.net now marks its patching incident as resolved. As of October 23, 2026, its official “PHP Update” notice reports: Patch rollout: October 22 at 5:17 a.m. EDT, upstream security patches were being deployed across its fleet, covering PHP 5.2–8.5. Resolved: The incident was marked resolved on October 22, 2026, at 6:36 a.m.
Based on the search results, here is what is known about PHP2Shell and Rocket.net: What Is PHP2Shell (CVE-2026-109618 & CVE-2026-109619)? PHP2Shell (CVE-2026-109618 and CVE-2026-109619) is a pair of Remote Code Execution vulnerabilities in PHP that let an attacker run their own code on a web server without logging in. The PHP security team rates both CVSSv4.0 9.2 and says
Yes. Rocket.net was affected because PHP2Shell is a PHP-core vulnerability, meaning PHP installations serving web requests—not a specific WordPress host—were in scope. Rocket.net reported on October 21 that it was rolling out patches across every PHP version from 5.2 through 8.5. By October 22, the available source reported Rocket.net’s remediation as underway, but did not explicitly confirm that every
Captured . No status named. Cites a rocket.net page.
Yes, Rocket.net was affected by the PHP2Shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619), and it has deployed rolling patches across its server fleet. Status & Patching Details Affected Status: All PHP versions from 5.2 through 8.5 across Rocket.net infrastructure were exposed to the core PHP remote code execution (RCE) flaws. Patch Rollout: Rocket.net initiated rolling wave deployments of upstream security patches
Rocket.net is rolling out patches for all hosted PHP versions (ranging from PHP 5.2 through PHP 8.5) to address the PHP2Shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619). Key Details from Rocket.net's Status / Rollout Status: Currently rolling out updates across their infrastructure. Affected PHP Versions: Covers PHP versions from 5.2 to 8.5. How to Verify: Your exposed PHP version number may
One card per engine, the latest capture. Every capture is in ai-answers.json. Answers are captured through the engines' APIs and Google's answer surfaces, verbatim, with cited URLs, under the Broadcastwell method v1.1; one answer per engine per question per day for the watch.
Submit a correction or your statement
Submit a correction or your statement. We list a statement only once we have opened it on your own domain or verified official account. Disputes follow the dispute policy. Or email the statement link to index@broadcastwell.com.
Badge
The badge for Rocket.net reads PHP2Shell statement listed, Verified 23 October 2026, Broadcastwell, and links to this record. Badge and embed code · Badge terms.
Rocket.net's customers can ask us for the PHP2Shell Record Check: we capture what ChatGPT, Claude, Perplexity, Google AI Overviews and Google AI Mode say about Rocket.net and PHP2Shell, trace every wrong or missing statement to its source and deliver a statement page in the format the engines quote. Record Check $490 once.
About this page
This index reports published statements and AI answers on stated dates. It is not a security assessment. For patching, follow PHP's advisory and your host.