Research collected from outside sources and what this site derives from them; every fact links to a saved copy of its source Research or story?
Briefing for Taylor, project or programme manager · Plain English · from the same 70 claims, selected and ordered for one reader
What unplanned work does this create, who do I chase, and what do I tell stakeholders?
This briefing v5 written in site v0.5.9 on 22 October 2026 · history and changes, 4 earlier
The answer in thirty seconds
Expect unplanned work this week: updating PHP on every system that uses it, restarting, and re-testing. Some teams may take systems offline for hours as a precaution. Anything still on PHP 8.1 or older has no ready-made fix and becomes a migration project. Ask each system owner for a patch date and a test plan.
This is a platform event, not an application bug, so it lands on every team that ships anything running on PHP at once. Plan for it the way you would plan for a datacentre move: an inventory, an owner per system, a date, a test.
What to decide or do
- Get the list. Which systems run PHP, who owns each, and which are on the internet. Vendor products and hosting panels count. Without the list nothing else can be scheduled.
- Get a date per system. Updating PHP means installing the fixed version, restarting, rebuilding containers and re-testing. Internet-facing systems first.
- Budget for regression testing. The fix changes how PHP behaves when it runs short of memory: a system that used to limp along may now stop cleanly. Load tests are worth running before the release, not after.
- Plan for precautionary downtime. Agencies advise isolating or taking offline what cannot be updated in time. Agree with stakeholders now who can make that call, how long it may last, and what users see meanwhile.
- Treat PHP 8.1 and older as a project. There is no ready-made release for them. Moving to a supported version is a migration with its own scope and schedule.
- Expect a second round. A report that the first fix may be incomplete is open. Keep a slot free in the next fortnight.
Your reading path
- Your briefing 4 min
- Explained from the start 6 min
- If you run PHP 3 min
- Impact: offline vs compromised 2 min
- Timeline 1 min
About 16 minutes in all. Choose read as Taylor and the bar under the menu keeps your place on every page.
What this briefing covers
- what unplanned work this creates
- which systems and owners to chase
- what to tell stakeholders about downtime
- what changes after the fix
What you can skip
- the code
- the bug classes
- the detection rules
Words you will meet
PHPPatchPrimary sourceNSACISANCSCExploit, exploitationWeb serverphp2shellRemote code execution (RCE)Evidence vaultCVEGitHub advisory (GHSA)Honeypot
Each is underlined where it first appears; hover or tap for a one-line definition, or open the glossary.
The facts this rests on
Show the 20 claims behind this briefing, each with its status and sources
- confirmed two or more primary sources agree, or the fact was counted from a captured file
- reported one party says so, and it has not been contradicted
- disputed the sources disagree, and both readings are shown
- contradicted a primary source says otherwise
- unverified even the reporting outlet could not check it
- p/n primary sources among the n cited; a blocked capture is counted and marked
| Claim | Who says it | Status | Fact-check | Primary | Sources |
|---|---|---|---|---|---|
| If an immediate update is not feasible, take the system offline until it can be fully mitigated X post 13:45:58Z 21 October (10.1 million views at capture) and the press release. fact timeline → | NSA Cybersecurity | confirmed | A6 Established●●●●●● | 2/2 | NSA Cyber on X NSA |
| Organisations that cannot update immediately, or that run PHP 8.1 or older, should take PHP-based systems offline fact timeline → | CISA | confirmed | A6 Established●●●●●● | 1/1 | CISA |
| Edge protections went live hours before disclosure: Cloudflare at 03:02 UTC; Imperva, Akamai and Fastly on 21 October; Fortinet signatures by 22 October Every vendor says the same two things: it is a stopgap, and patch anyway. fact timeline → | the vendors | confirmed | A2 Reported●●○○○○ status overstated | 5/5 | Cloudflare Imperva Threat Research Akamai Security Research Fastly Fortinet Community |
| The risks require immediate patching across United States Government departments and agencies No CISA emergency directive was visible on the CISA home page at capture. fact timeline → | NSA | reported | A6 Established●●●●●● | 1/2 | NSA CISA |
| 'Where immediate remediation is not feasible, organisations should consider taking the system offline until it can be fully mitigated' That sentence is not on the NCSC page as captured at 08:09Z on 22 October. The page's offline advice is step 4 of 6 and is worded differently. The page was modified at 07:30Z that morning. The sentence's opening matches the Canadian CCCS text. fact timeline → | UK NCSC, as quoted by the BBC | disputed | A2 Reported●●○○○○ disputed | 2/3 | BBC News NCSC UK CCCS |
| The UK's NCSC, the NSA and their counterparts in the EU and Australia advise taking systems offline where patching is not feasible Australia's ACSC gives no offline advice. CERT-EU says isolate. The Netherlands, Italy, Japan and New Zealand give no offline advice. fact timeline → | BBC | contradicted | A1 Weak signal●○○○○○ | 4/6 | BBC News ACSC CERT-EU NCSC-NL ACN / CSIRT Italia JPCERT/CC |
| Latvia restricted access from abroad to several state digital resources, possibly until 26 October; lsm.lv and 112.lv were restored by 20:00 UTC The one documented case of government services being pulled from the public internet, from the agency itself. fact timeline → | CERT.LV | confirmed | A6 Established●●●●●● | 1/1 | CERT.LV |
| The Dutch NCSC took its own site offline as a precaution, as did DigiD, MijnOverheid and Overheid.nl, with no signs of active exploitation of those services Primary statement. fact timeline → | the Dutch government | confirmed | A3 Echoed●●●○○○ status overstated | 1/2 (1 blocked) | Rijksoverheid / NCSC-NL Dutch IT Leaders |
| Weird Gloop turned off its wiki web servers for 13 hours and still served about 94% of page views from cache Primary, and the one outage with a measured cost. fact timeline → | Weird Gloop | confirmed | A2 Reported●●○○○○ status overstated | 1/1 | Weird Gloop |
| Parts of Wikipedia, Edinburgh council, French government sites, the University of Geneva, online shops and the BBC were affected or taken offline Not captured from any of the named organisations. fact timeline → | BBC | reported | A2 Reported●●○○○○ | 0/1 | BBC News |
| As of 20:50 UTC on 22 October, no named organisation has said it was compromised through php2shell. Exploitation attempts are widely reported, and two security vendors, Hadrian and Patchstack, report successful exploitation without naming any victim. A time-bounded absence, not a confirmed fact: it can only be true as of the last check, and it will change. Changed from "confirmed" on 22 October at the editor's request (fact-check run 1 had marked it overstated; Perplexity and ChatGPT, asked by the editor, said the same). Attempts are not compromises: watchTowr says "nobody has been successful to date"; Amazon says it is unclear whether any attempt would have succeeded on real systems; Patchstack's incidents are reports from hosting partners with no victim named. Source watch (vault oq9gflln), pending promotion into the evidence vault: the PHP Foundation's executive director told The Verge and WIRED "to our knowledge, there has been no successful attempt at remote code execution" (raw/us/tech-press/the-verge/php2shell-websites-down/); officials in Germany, the Netherlands and Japan say they have not seen an attack succeed (The Next Web, raw/nl/tech-press/the-next-web/php2shell-no-confirmed-breaches/); GMO confirmed a break-in on 20 October on its FX trading VPS service (26,739 servers, logins possibly taken) without stating the cause (raw/jp/news/yahoo-news-jp/gmo-fx-login-leak/20261022T191523Z/); Czech Technical University says it stopped an active attack that was part of worldwide attempts against PHP sites, success not established (raw/cz/tech-press/lupa/cvut-cyber-attack/20261022T191510Z/); Valtec in Japan blamed php2shell for a break-in, then retracted: its own service's flaw (raw/jp/tech-press/impress-watch/valtec-php-attack/20261022T191433Z/); Fortune reports an anonymous startup owner alleging stolen source code, unnamed and not attributed to the flaw. Edited by researcher@php.newsroom. fact timeline → | this site, from every captured source in the evidence vault and the source watch, as of 20:50 UTC on 22 October | reported | A4 Corroborated●●●●○○ status overstated | 6/9 | CISA CISA Huntress Amazon SecurityWeek SecurityWeek Recorded Future Imperva Threat Research Weird Gloop |
| Finland's state IT provider Valtori restricted public traffic to government web services from 12:45 local time on 21 October as a precaution fact timeline → | Yle; Helsinki Times, quoting Valtori | reported | A2 Reported●●○○○○ | 0/2 | Yle Helsinki Times |
| The Wikimedia Foundation took down a number of systems 'as a precautionary measure until they can be safely patched' No Wikimedia-published statement captured. fact timeline → | the Foundation, as quoted by CNN and The Cyber Express | reported | A4 Corroborated●●●●○○ | 0/2 | CNN The Cyber Express |
| Edinburgh council's site went offline late on 21 October; the council called it 'essential maintenance' and did not confirm a link fact timeline → | The Scotsman quoting the council | reported | A3 Echoed●●●○○○ | 0/1 | The Scotsman |
| Oxford City Council: 'a precaution because of a worldwide issue with the underlying technology and is not a cyber incident' fact timeline → | the council's social post, via Oxford Chronicle | reported | A2 Reported●●○○○○ | 0/1 | Oxford Chronicle |
| Edinburgh and Oxford councils, the Met Police and the Office for Budget Responsibility were unavailable; Bristol, Lambeth and Barnet council sites showed errors fact timeline → | LBC; Insurance Business | reported | A3 Echoed●●●○○○ | 0/2 | LBC Insurance Business |
Counted from the repository, not from a page. Five authors; 389 files; 10,689 insertions. fact timeline → | php/php-src commit 3584a98bd, read from a clone | confirmed | A6 Established●●●●●● | 2/2 | php/php-src, read from a clone php-src |
| The fixes were released at 14:00 UTC on 21 October CERT-EU says 13:30 UTC; the tags and advisories are stamped 13:34 to 13:35 UTC; the GitHub release 14:06 UTC; the php.net feed entries carry 00:05 to 00:35 UTC, which are authoring times, not publication times. fact timeline → | php.net pre-announcement; Daubois; CERT-FR (16:00 Paris) | disputed | A2 Reported●●○○○○ disputed | 7/8 | oss-security Daubois CERT-FR CERT-EU php-src PHP php-src php.net |
| The pre-announcement was published at 19:30 UTC on 20 October The php.net feed says 20:32 UTC; oss-security relayed it at 20:22:51 UTC, so it was public by then. fact timeline → | PHP Foundation | disputed | A2 Reported●●○○○○ disputed | 3/3 | PHP Foundation oss-security php.net |
| The flaws were disclosed on 22 October 2026 Primary sources put the release at 21 October: GHSAs 13:34Z, tags 13:35Z, CVE records 13:48Z and 13:54Z, GitHub release 14:06Z. fact timeline → | BBC framing (UK morning coverage) | contradicted | refuted measures differently | 2/3 | BBC News php.net php-src |
Every sentence above rests on these rows. They are folded away because they are written in the sources' own vocabulary; the glossary explains each term.
What is still open
- Who first leaked the CVE IDs on 20 October, and where. The PHP Foundation does not say; a PHP security team member points to an anonymous Hacker News post. No copy of that post is in the vault.
- Whether the deleted Calif video is the one now embedded on Calif's own write-up. Calif's page does not mention the leak.
- Whether any site was actually compromised before it was patched or taken offline. Every claim of exploitation so far is of attempts, probes or honeypot hits.
- Which sites were really taken offline, and why. The BBC's list (parts of Wikipedia, Edinburgh council, French government services, the University of Geneva, the BBC itself) has not been captured from any of those organisations. Latvia's geo-blocking is the one documented case, from the agency itself.
- Whether the 8.5.12 fix is complete. A Fediverse report of a third bug or incomplete fix reached oss-security on 21 October; PHP reportedly told Canonical it is unrelated. Nothing from PHP on the list yet.
The full set of claims is on every claim; the ordered steps for a vulnerable system are on if you run PHP. Other readers: Curious reader · Website owner · Board member or executive · Security lead · PHP or platform engineer · Journalist · Security researcher · Analyst or policy advisor · CISO · CTO · CFO · Data protection officer · Head of AppSec · Developer · Communications team.