All incidents
Security incidentDegradedResolved

Critical PHP vulnerabilities (PHP2Shell): CVE-2026-109618 and CVE-2026-109619

From 23:30 on 20 October 2026 to 04:30 on 23 October · 2 days 5 h

  1. Investigating—
  2. Identified23:30
  3. Monitoring01:19
  4. Resolved04:30

Updates

  1. Resolved

    23 October 2026 · 04:30

    Upgraded to official versions: CloudLinux released builds carrying the official PHP version numbers (alt-php at 03:08, ea-php at 16:10). We upgraded PHP to 8.2.35, 8.3.36, 8.4.27 and 8.5.12.

  2. Monitoring

    22 October 2026 · 09:41

    alt-php hardened: We installed patched alt-php packages for all versions from 5.2 to 8.5, then restarted the services.

  3. Monitoring

    22 October 2026 · 02:00

    Scheduled restart: We restarted the server to apply a kernel update and to ensure every PHP process was running the patched builds.

  4. Monitoring

    22 October 2026 · 01:19

    ea-php hardened: We installed CloudLinux’s patched EasyApache 4 packages for all ea-php versions. CloudLinux added the fix to the existing builds while keeping their version numbers (for example, 8.4.26). We then restarted the PHP services.

  5. Identified

    21 October 2026 · 22:30

    Our team began tracking CloudLinux releases and applying updates as soon as they were available.

  6. Identified

    21 October 2026 · 18:00

    PHP released versions 8.2.35, 8.3.36, 8.4.27 and 8.5.12.

  7. Identified

    21 October 2026 · 13:08

    CloudLinux released Imunify360 protection rules (ruleset 8.83) to block known exploit attempts.

  8. Identified

    20 October 2026 · 23:35

    The PHP Security Team announced an emergency security release for the two vulnerabilities.

  9. Identified

    20 October 2026 · 23:30

    Two critical PHP vulnerabilities (CVSS v4 9.2) allowed remote code execution without authentication. They affected every PHP setup that serves websites. We have updated all PHP versions on our hosting servers, and shared hosting customers do not need to take any action.

Post-incident report

What happened

On 20 October 2026, two critical PHP vulnerabilities known as PHP2Shell came to light: CVE-2026-109618 and CVE-2026-109619, rated 9.2 under CVSS v4. They allowed remote code execution without authentication and affected every PHP setup that serves websites, including our hosting servers.

Services involved

cPanel hosting, Running CoreVPS servers, Illevante website, Help center, Illevante community and Technical support.

Impact on customers

Shared hosting customers did not need to take any action; our team updated every PHP version on our hosting servers.

Why

The flaw was in PHP itself, not in how our services are set up, so a complete fix depended on the official release from the PHP Security Team and then on CloudLinux’s patched PHP packages, which we run PHP from on our servers.

Timeline Dubai time

  1. 20 October · 23:30

    The incident began: two critical PHP vulnerabilities.

  2. 20 October · 23:35

    The PHP Security Team announced an emergency security release for the two vulnerabilities.

  3. 21 October · 13:08

    CloudLinux released Imunify360 protection rules (ruleset 8.83) to block known exploit attempts, as a stopgap until the fix.

  4. 21 October · 18:00

    The official fix came out: PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12.

  5. 21 October · 22:30

    Our team began tracking CloudLinux releases to apply updates as soon as they were available.

  6. 22 October · 01:19

    We installed CloudLinux’s patched ea-php packages for every version, then restarted the PHP services.

  7. 22 October · 02:00

    We restarted the server to apply a kernel update and to make sure every PHP process ran the patched builds.

  8. 22 October · 09:41

    We installed patched alt-php packages for every version from 5.2 to 8.5, then restarted the services.

  9. 23 October · 04:30

    We upgraded PHP to the official versions 8.2.35, 8.3.36, 8.4.27 and 8.5.12 once CloudLinux released them under their official numbers, and closed the incident.

What we fixed

We updated every PHP version on our hosting servers to patched builds, first with CloudLinux’s packages that added the fix to the existing versions, then with the official releases, and restarted the services and the server so that every PHP process runs the patched code.

What we do from now on

We track CloudLinux’s security releases and apply their updates as soon as they are out.