---
title: PHP2Shell Vulnerabilities Took Government Sites Offline
description: The PHP2Shell vulnerabilities let anyone run code on a PHP server with one request. Government sites across Europe went offline until the fix shipped.
canonical: https://lukeocodes.dev/php2shell-vulnerabilities-government-sites-offline
type: article
locale: en_GB
published: 2026-10-24T00:00:00.000Z
modified: 2026-10-24T00:00:00.000Z
authors:
  - Luke Oliff
section: Security
tags:
  - Security
  - News
  - AI
  - php
  - php2shell
  - cve
  - europe
  - open source
  - wordpress
  - weekend
feed: https://lukeocodes.dev/rss.xml
search: https://lukeocodes.dev/search.json?q={query}
schema:
  - "@context": https://schema.org
    "@graph":
      - "@type": WebSite
        "@id": https://lukeocodes.dev/#website
        url: https://lukeocodes.dev
        name: Luke Oliff
        alternateName: lukeocodes
        inLanguage: en
        publisher:
          "@id": https://lukeocodes.dev/authors/luke#person
        description: Personal blog and writing by Luke Oliff — developer relations, voice AI, developer experience.
        potentialAction:
          - "@type": SearchAction
            target:
              "@type": EntryPoint
              urlTemplate: https://lukeocodes.dev/blog/search?q={search_term_string}
            query-input: required name=search_term_string
      - "@type": Person
        "@id": https://lukeocodes.dev/authors/luke#person
        name: Luke Oliff
        url: https://lukeocodes.dev/authors/luke
        description: Engineer and developer relations leader. Writing about developer relations, AI, and the voice industry, from the UK.
        mainEntityOfPage: https://lukeocodes.dev/authors/luke
        givenName: Luke
        familyName: Oliff
        image: https://lukeocodes.dev/authors/luke.jpg
        jobTitle: Engineer and developer relations leader
        sameAs:
          - https://www.linkedin.com/in/lukeocodes
          - https://github.com/lukeocodes
          - https://bsky.app/profile/lukeocodes.dev
          - https://x.com/lukeocodes
          - https://hashnode.com/@lukeocodes
          - https://dev.to/lukeocodes
        knowsAbout:
          - Developer Relations
          - Developer Experience
          - Voice AI
          - Text-to-Speech
          - Answer Engine Optimisation
          - Search Engine Optimisation
          - Open Source
          - Developer Tooling
          - API Design
          - Speech-to-Text
          - Voice Agents
          - Community Building
        knowsLanguage:
          - English
        nationality: British
        alumniOf:
          - "@type": Organization
            name: The Open University
  - "@context": https://schema.org
    "@graph":
      - "@type": Person
        "@id": https://lukeocodes.dev/authors/luke#person
        name: Luke Oliff
        url: https://lukeocodes.dev/authors/luke
        description: Engineer and developer relations leader. Writing about developer relations, AI, and the voice industry, from the UK.
        mainEntityOfPage: https://lukeocodes.dev/authors/luke
        givenName: Luke
        familyName: Oliff
        image: https://lukeocodes.dev/authors/luke.jpg
        jobTitle: Engineer and developer relations leader
        sameAs:
          - https://www.linkedin.com/in/lukeocodes
          - https://github.com/lukeocodes
          - https://bsky.app/profile/lukeocodes.dev
          - https://x.com/lukeocodes
          - https://hashnode.com/@lukeocodes
          - https://dev.to/lukeocodes
        knowsAbout:
          - Developer Relations
          - Developer Experience
          - Voice AI
          - Text-to-Speech
          - Answer Engine Optimisation
          - Search Engine Optimisation
          - Open Source
          - Developer Tooling
          - API Design
          - Speech-to-Text
          - Voice Agents
          - Community Building
        knowsLanguage:
          - English
        nationality: British
        alumniOf:
          - "@type": Organization
            name: The Open University
      - "@type": BlogPosting
        "@id": https://lukeocodes.dev/php2shell-vulnerabilities-government-sites-offline#article
        headline: PHP2Shell Vulnerabilities Took Government Sites Offline
        alternativeHeadline: PHP2Shell Vulnerabilities Took Government Sites Offline Across Europe
        description: The PHP2Shell vulnerabilities let anyone run code on a PHP server with one request. Government sites across Europe went offline until the fix shipped.
        datePublished: 2026-10-24T00:00:00.000Z
        dateModified: 2026-10-24T00:00:00.000Z
        url: https://lukeocodes.dev/php2shell-vulnerabilities-government-sites-offline
        mainEntityOfPage: https://lukeocodes.dev/php2shell-vulnerabilities-government-sites-offline
        inLanguage: en
        author:
          - "@id": https://lukeocodes.dev/authors/luke#person
        isPartOf:
          "@id": https://lukeocodes.dev/#website
        keywords: Security, News, AI, php, php2shell, cve, europe, open source, wordpress, weekend
        articleSection: Security
        about:
          - "@type": Organization
            name: PHP Foundation
          - "@type": Organization
            name: Wiz
          - "@type": Organization
            name: Cloudflare
          - "@type": Person
            name: Matthew Prince
        mentions:
          - "@type": Organization
            name: National Cyber Security Centre
          - "@type": Organization
            name: Palo Alto Networks
        abstract: Two bugs in PHP, the PHP2Shell vulnerabilities, let an attacker run their own code on a web server with one request and no login. Details leaked on 20 October 2026, PHP shipped fixed versions on 21 October, and government sites in the Netherlands, France, Denmark and Finland went offline until they were patched.
        speakable:
          "@type": SpeakableSpecification
          cssSelector:
            - .post-tldr
            - h1
        image: https://lukeocodes.dev/og.png?h=PHP2Shell+Vulnerabilities+Took+Government+Sites+Offline&d=The+PHP2Shell+vulnerabilities+let+anyone+run+code+on+a+PHP+server+with+one+request.+Government+sites+across+Europe+went+offline+until+the+fix+shipped.&e=Writing
        wordCount: 623
        timeRequired: PT4M
        publisher:
          "@id": https://lukeocodes.dev/authors/luke#person
      - "@type": BreadcrumbList
        itemListElement:
          - "@type": ListItem
            position: 1
            name: Home
            item: https://lukeocodes.dev
          - "@type": ListItem
            position: 2
            name: Writing
            item: https://lukeocodes.dev/blog
          - "@type": ListItem
            position: 3
            name: PHP2Shell Vulnerabilities Took Government Sites Offline
            item: https://lukeocodes.dev/php2shell-vulnerabilities-government-sites-offline
      - "@type": FAQPage
        "@id": https://lukeocodes.dev/php2shell-vulnerabilities-government-sites-offline#faq
        mainEntity:
          - "@type": Question
            name: How do I know if my site has the PHP2Shell vulnerabilities?
            acceptedAnswer:
              "@type": Answer
              text: Any PHP older than 8.2.35, 8.3.36, 8.4.27 or 8.5.12 that serves web requests is affected, however it runs (PHP-FPM, Apache mod_php, php-cgi, FrankenPHP). Run php -v on the server. If someone else runs the server, check their status page. Most big hosts patched on 21 October.
          - "@type": Question
            name: Is there a fix other than updating PHP?
            acceptedAnswer:
              "@type": Answer
              text: No complete one. PHP's release notes say updating is the only safe choice. Web firewalls (filters that sit in front of a site) added rules for the known attack shapes, which helps until you patch. The UK NCSC says if you can't patch or filter quickly, take the system offline.
          - "@type": Question
            name: Why did the PHP2Shell details leak early?
            acceptedAnswer:
              "@type": Answer
              text: The fix was scheduled for 21 October at 14:00 UTC (3pm in the UK). On 20 October the bugs turned up on Hacker News, watchTowr posted about them on X, and Calif, one of the firms that found them, put out a demo video by mistake. PHP shipped the fix 26 minutes early.
---

[Luke Oliff.](/)

- [Blog](/blog)
- [CV](/cv)
- [Uses](/uses)
- [User manual](/user-manual)
- [Living with ADHD](/living-and-working-with-adhd)
- [RSS](/rss.xml)

[Luke Oliff · Writing](/blog)

# PHP2Shell Vulnerabilities Took Government Sites Offline Across Europe

Oct 2026 · [Security](/blog/category/security) · 4 min read · [Luke Oliff](/authors/luke)

Two bugs in PHP, the PHP2Shell vulnerabilities, let an attacker run their own code on a web server with one web request and no login ([Help Net Security](https://www.helpnetsecurity.com/2026/10/21/php2shell-php-vulnerabilities-patched-cve-2026-109618-cve-2026-109619/)). Details leaked on 20 October 2026, and government sites in the Netherlands, France, Denmark and Finland went offline until PHP shipped fixed versions on 21 October.

## What the PHP2Shell vulnerabilities are

PHP runs about seven in ten websites. The two bugs, CVE-2026-109618 and CVE-2026-109619 (a CVE is the public ID for a security bug), sit in how PHP cleans up when a request runs out of memory or crashes, and the server runs what you sent it before the site's own code starts ([php.net](https://news-web.php.net/php.announce/511)). PHP has known about one of them since 2024 and couldn't agree a fix, which the PHP Foundation now calls "a structural failure" ([The Next Web](https://thenextweb.com/news/php-foundation-structural-failure-2024-flaw-leak)).

Ryan Austin at the security firm Calif ([Wikipedia](https://en.wikipedia.org/wiki/PHP2Shell)) and a team at Wiz, using the AI models Gemini 4 Argon and GPT-5.6 Sol ([Wiz](https://www.wiz.io/blog/php2shell-php-rce)), found them separately in August. The fix was scheduled for 21 October at 14:00 UTC (3pm in the UK). On 20 October the bugs appeared on Hacker News, watchTowr posted about them on X, and Calif put out a demo video by mistake. PHP published 8.5.12, 8.4.27, 8.3.36 and 8.2.35 at 13:34 UTC, 26 minutes early.

## Who went offline

The Netherlands took down DigiD (the national login), MijnOverheid, Overheid.nl and the parliament website on Wednesday morning, before a fix existed ([NL Times](https://nltimes.nl/2026/10/21/dutch-parliament-website-taken-offline-cybersecurity-warning-triggers-precautions)). Matthijs van Amelsfort of the Dutch NCSC said there was no sign of attacks, but traffic showed people scanning sites for the PHP2Shell vulnerabilities ([NL Times](https://nltimes.nl/2026/10/22/important-dutch-websites-still-offline-php-issues)). Most were back by Thursday morning.

France's Interior Ministry took every prefecture (local government office) website offline ([The Connexion](https://www.connexionfrance.com/news/french-prefecture-websites-taken-offline-after-critical-security-flaws-found/823055)). Denmark's council IT firm Kombit shut the national school messaging platform, and Finland's state IT provider Valtori took government public services offline ([Reuters factbox](https://www.globalbankingandfinance.com/factbox-websites-taken-offline-over-php-risks/)).

## What happened after the patch

Amazon's threat team saw attack attempts on 17 October, four days early ([Help Net Security](https://www.helpnetsecurity.com/2026/10/21/php2shell-php-vulnerabilities-patched-cve-2026-109618-cve-2026-109619/)). Palo Alto's Unit 42 counts 22.6 million PHP servers still reachable from the internet. In one European government body, attackers used an AI agent to pull stored passwords and the secrets behind two-step login within two hours of getting in ([Unit 42](https://unit42.paloaltonetworks.com/cve-2026-109618-cve-2026-109619/)).

Cloudflare's Matthew Prince told Reuters on 23 October that he knows of "a bunch of additional severe vulnerabilities" and expects "a couple of years" where "every single week it's going to feel like the sky is falling" ([Reuters via TimesLive](https://www.timeslive.co.za/news/sci-tech/2026-10-23-experts-warn-of-more-outages-as-ai-uncovers-software-flaws/)).

## FAQ

### How do I know if my site has the PHP2Shell vulnerabilities?

Any PHP older than 8.2.35, 8.3.36, 8.4.27 or 8.5.12 that serves web requests is affected, however it runs (PHP-FPM, Apache mod_php, php-cgi, FrankenPHP). Run `php -v` on the server. If someone else runs the server, check their status page. Most big hosts patched on 21 October.

### Is there a fix other than updating PHP?

No complete one. PHP's release notes say updating is the only safe choice. Web firewalls (filters that sit in front of a site) added rules for the known attack shapes, which helps until you patch. The UK NCSC says if you can't patch or filter quickly, take the system offline.

### Why did the PHP2Shell details leak early?

The fix was scheduled for 21 October at 14:00 UTC (3pm in the UK). On 20 October the bugs turned up on Hacker News, watchTowr posted about them on X, and Calif, one of the firms that found them, put out a demo video by mistake. PHP shipped the fix 26 minutes early.

The bugs waited two years for a fix and the models found them in one summer, so the next PHP2Shell has probably already been found.

[← Newer: DevRel This Week, 26 October: Developers Ship Faster and the Friction Stayed](/devrel-this-week-26-october-2026)

[All posts](/blog) →

## Search this site

`GET https://lukeocodes.dev/search.json?q=<words>` returns matching posts as JSON, each with its page URL and its markdown URL. Add `&limit=<1-50>` for more than 10. How it works: [/blog/search](https://lukeocodes.dev/blog/search.md).

```sh
curl "https://lukeocodes.dev/search.json?q=developer+relations"
```

---

© 2026 Luke Oliff. Posts live at the root of this site.

- [GitHub](https://github.com/lukeocodes)
- [LinkedIn](https://www.linkedin.com/in/lukeocodes)
- [X](https://x.com/lukeocodes)
- [Bluesky](https://bsky.app/profile/lukeocodes.dev)
- [Email](mailto:luke@lukeoliff.com)
- [RSS](/rss.xml)

## Cookies

This site sets one analytics cookie, from Google Analytics, and only in a browser that accepts the cookie banner. A client that does not run scripts sets no cookies, so there is nothing to accept or decline here.

[Cookie policy](/cookies)
