Opens in a new tab

Daily Security Briefing: Sunday, October 25, 2026

  • Home
  • Blog
  • Daily Security Briefing: Sunday, October 25, 2026
Managed Technology daily security briefing on PHP2Shell critical flaws cracking open a server
Updated October 25, 2026 at 5:51 PM ET

This security briefing covers one actively exploited issue: emergency PHP updates that fix two critical remote code execution flaws. The PHP development team has released fixes for two vulnerabilities, tracked as CVE-2026-109618 and CVE-2026-109619 and together named PHP2Shell. The flaws could let attackers run code remotely on web servers without logging in, and each is rated 9.2 (Critical) under CVSS v4.0.

If your site or a web tool your business relies on runs on PHP, these fixes apply to you.

What happened

The PHP development team shipped emergency security updates for two critical remote code execution vulnerabilities named PHP2Shell, tracked as CVE-2026-109618 and CVE-2026-109619, each rated 9.2 (Critical) under CVSS v4.0. The security firm watchTowr, which published its own analysis, states that "watchTowr has observed exploitation of both CVE-2026-109618 and CVE-2026-109619 in the wild." watchTowr credits the discovery to the security research team at Calif.

Are you affected?

Anyone running PHP is affected, and the development team is urging all PHP users to update; the source gives no number. The UK’s National Cyber Security Centre says organisations using any version of PHP are affected and that all versions may be affected, so the issue is not limited to outdated releases. watchTowr notes that internet-facing servers running PHP as an Apache module carry the highest demonstrated risk, and that systems on PHP 8.1 or older no longer receive official PHP updates. You can gauge your exposure by asking your IT team or hosting provider which PHP version each of your websites runs and whether that system is reachable from the internet.

What to do now

  1. Ask your IT team or hosting provider which version of PHP your websites and web applications run, and whether updates are applied automatically or need to be scheduled.
  2. Deal with internet-facing systems first. The NCSC advises organisations to "Identify systems running PHP across your infrastructure, prioritising internet-facing systems."
  3. Confirm the update was applied, and ask whether a web application firewall or virtual patching protects those sites while the work is scheduled. The NCSC notes the PHP Foundation has published temporary mitigations for systems that cannot update right away.
  4. Flag anything still on PHP 8.1 or older. watchTowr reports those branches no longer receive official PHP updates and need a distribution backport or an upgrade to a supported version.

Background

watchTowr’s timeline states that on October 20, 2026, after embargo leaks were observed, it publicly confirmed the rumored PHP vulnerabilities were real, and that the PHP security team gave advance notice of a security release set for October 21, 2026, at 14:00 UTC covering two critical vulnerabilities each rated CVSS v4.0 9.2. watchTowr’s published table marks both CVE-2026-109618, described as remote code execution via out-of-memory corruption, and CVE-2026-109619, described as remote code execution via stale global state, as exploited in the wild.

FAQ

What is PHP2Shell?

PHP2Shell is the name for two critical remote code execution vulnerabilities in PHP, tracked as CVE-2026-109618 and CVE-2026-109619, each rated 9.2 (Critical) under CVSS v4.0, according to watchTowr.

Which PHP versions contain the fix?

Fixes are available in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35.

Are these flaws being exploited?

watchTowr states that it has observed exploitation of both CVE-2026-109618 and CVE-2026-109619 in the wild.

This article reports on publicly available information from the sources listed below. We have no reason to believe it is inaccurate, but we have not independently verified every claim, and details may change as the story develops.

Sources

← All Articles