EDITION OF THU 22 OCT 2026
05 · WORLD

Governments take websites offline as critical PHP flaws prompt urgent patching

publishers 62articles 75first reported 21 Oct, 02:12 UTCdeveloping since 21 Oct · 11 editionstop 25 #5

Government agencies and businesses took websites and online services offline this week while installing emergency fixes for two critical vulnerabilities in PHP, the server-side programming language used by nearly 70% of websites whose underlying language is known.

The flaws, dubbed “PHP2Shell” and identified as CVE-2026-109618 and CVE-2026-109619, could allow an unauthenticated attacker to execute code remotely on vulnerable servers. Potential consequences include data theft, website defacement and broader system compromise. Researchers said the weaknesses had remained in PHP for more than a decade before teams using artificial intelligence tools identified workable attack paths.

The PHP Foundation released patched versions — 8.2.35, 8.3.36, 8.4.27 and 8.5.12 — on Wednesday. Cybersecurity authorities advised operators to update immediately and temporarily disconnect systems that could not be patched. Updating website themes or plugins alone does not address the underlying PHP vulnerabilities.

Public services were disrupted across Europe. The Netherlands took down government portals and its DigiD identity service, while Finland, France, Germany and the United Kingdom restricted or disabled some services as precautions. Britain reported 32 government services unavailable and four partially unavailable, while saying no major public-facing critical services were affected. Ghana gave government institutions seven days to identify and remediate vulnerable systems.

Reports differed on exploitation activity. The PHP Foundation said Wednesday that it had no evidence of a successful working exploit, and British officials reported no known breaches. Amazon Threat Intelligence reported observing an exploit attempt, while security researchers said they had reproduced a working exploit. Authorities urged organizations to inspect logs and systems for signs of compromise after patching.

HOW THIS STORY WAS MADE

Written from 8 articles, 6 with the publisher's own text; 8 independent newsrooms once syndicated copies count as one; this version written 36 h after the record first saw the story; the editor kept it as written.

Publishers
62
Source articles
75
Given to the writer
8, 6 with the article's own text
Independent newsrooms
8
This version written
36 h after the record first saw the story
Second model (editor)
kept as written
Publication gate
passed
Human review
none

WHAT THE EDITOR DID

The second model checked the writer's draft against the same sources and published it as written.

Written by a language model from the sources above, then checked by a second model that may only cut, attribute or correct. How it works →

NAMED IN THE COVERAGE

OUTLETS CARRYING THE STORY, RUN BY RUN

0 33 67 22 Oct 23 Oct 24 Oct 25 Oct 26 Oct 27 Oct 28 Oct 29 Oct 30 Oct 31 Oct 21 Oct 18:25 UTC · PHP releases emergency patches for two critical remote-code flaws 22 Oct 00:14 UTC · Emergency PHP patches issued as critical flaws prompt global website shutdowns 22 Oct 06:10 UTC · PHP releases emergency patches as governments take websites offline 22 Oct 12:11 UTC · Governments and companies rush to patch critical PHP flaws 22 Oct 18:11 UTC · Governments take websites offline as critical PHP flaws prompt urgent patching 23 Oct 14:14 UTC · Governments take websites offline as critical PHP flaws trigger global patching effort 23 Oct 18:13 UTC · Governments take websites offline as critical PHP flaws prompt global patching effort 25 Oct 06:14 UTC · Governments take websites offline after critical PHP flaws disclosed 26 Oct 00:18 UTC · Critical PHP flaws prompt governments and businesses to take websites offline

WHAT HELD, WHAT CAME LATER

From the first reports to the latest

  • Wiz Atlas · 3 outlets

Entered the story later

  • Wikimedia Foundation · from 23 Oct 14:02, 2 outlets

Figures reported with different numbers

  • all websites: 70% (3 from 21 Oct 18:15) → 69.3% (1 from 21 Oct 20:36) → 40% (1 from 22 Oct 12:00)

Matched by pattern, not read: a different number can be a correction, a rising count, or two different counts.

HOW THIS STORY DEVELOPED: EVERY HEADLINE, EVERY OUTLET →