Government advisories · CERT-EU / NCSC · 5 sourced facts

CERT-EU, NCSC and CISA issue alerts as some sites go offline

The official advice is consistent: patch immediately, restart workers, and isolate if that is not possible. Some organisations chose to take services offline rather than wait.

Published22 October 2026 Event date21 October 2026 Last substantive update22 October 2026, 16:45 UTC Reading time1 min

Key facts

Each fact is linked to the source that supports it.
  1. CERT-EU advisory 2026-018 recommends immediate patching and says organisations should isolate internet-facing applications if patching is not immediately possible. CERT-EU
  2. The UK NCSC says organisations using any version of PHP are affected and should consider taking a system offline if mitigations cannot be applied quickly. UK National Cyber Security Centre
  3. CISA said it had not observed exploitation at the time of publication and urged immediate patching, according to CyberScoop. CyberScoop
  4. SecurityWeek reported that hundreds of sites went offline on 21 October, with European government, hospital and school sites among those affected. SecurityWeek
  5. Japan's IPA published an alert on 22 October and did not state that exploitation had been observed. IPA (Japan)

The official advice

Three national or regional bodies published advice within a day of the PHP release. CERT-EU’s advisory 2026-018 recommends immediate patching, vendor backports where available, and isolation of internet-facing applications if patching cannot happen immediately. The UK NCSC said organisations using any version of PHP are affected, told them not to limit discovery to outdated versions, and advised considering taking a system offline if mitigations cannot be applied quickly.

CISA, according to CyberScoop, said it had not observed exploitation at the time of publication and urged immediate patching. Japan’s IPA published its alert on 22 October without asserting that exploitation had been observed. These statements are not identical, and the difference matters.

Where the agencies differ

The agencies are describing the same technical situation with different evidence cut-offs. “No exploitation observed by this agency at this time” is narrower than “no exploitation has occurred”. It is also narrower than “the vulnerability is not being exploited”. Readers should preserve that distinction instead of compressing it into a single reassuring sentence.

The practical advice converges. Patch to 8.2.35, 8.3.36, 8.4.27 or 8.5.12. Restart PHP workers. If that is impossible, apply the official interim controls and reduce exposure, with isolation as the fallback when the controls cannot be applied quickly. Then look for evidence of compromise, because a clean application log does not clear a host.

Sites going offline

SecurityWeek reported that hundreds of sites went offline on 21 October, including European government, hospital and school sites. That is a real operational choice, not a failure of the advisory. For an organisation that cannot verify its PHP runtime quickly, taking a service offline can be safer than serving requests through an exposed worker. The cost is availability; the decision belongs to the operator, not to a generic checklist.

Sources for this page

Revision history

Time (UTC) Recorded change
22 October 2026, 16:45 UTC Added IPA and separated each agency's exploitation language from the others.
22 October 2026, 16:45 UTC Current published version.

This is an independent summary written by PHP2Shell Live. It is not a republished article and is not an official notice from PHP, any vendor or any agency. Read the editorial policy.

Search PHP2Shell Live

Type to search the local index Results stay in your browser
↑ ↓ move Enter open Esc close