HackSpotby Amethyst Apps
How it worksWhat we checkPricingGuidesInsightsAbout
Log inCheck my website
HackSpot / Insights

PHP2Shell timeline: what happened and when

A dated timeline of PHP2Shell (CVE-2026-109618 and CVE-2026-109619), from discovery in August 2026 to the 21 October fixes. Primary sources only.

By HackSpot team (Amethyst Apps) · October 23, 2026 · Updated October 25, 2026 · 3 min read

HackSpot: PHP2Shell timeline, what happened and when

The short version: the flaws were found in August 2026, reported to the PHP project privately, pre-announced on 20 October and fixed on 21 October 2026. Security agencies and companies published advice the same day. This timeline uses only what the organisations involved published themselves, and we'll update it as things change. If your site runs PHP, check it free.

Timeline

Date (2026)What happenedSource
19 AugustWiz Research finds the first of the PHP flaws.Wiz
20 to 21 AugustWiz confirms unauthenticated remote code execution in testing against Drupal, then WordPress.Wiz
24 AugustWiz reports the flaws to the PHP security team.Wiz
21 SeptemberThe PHP project acknowledges the reports and starts a coordinated fix.Wiz
20 Octoberphp.net pre-announces a critical security release for 21 October at 14:00 UTC, fixing two vulnerabilities rated CVSS v4.0 9.2.php.net
20 to 21 OctoberDetails of the flaws leak online before the fixes are out, so the PHP project brings its planned release forward, as its notice said it might.BBC News, php.net
21 OctoberPHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 are released with a security advisory for CVE-2026-109618 and CVE-2026-109619. Minimal source backports are published for 7.4, 8.0 and 8.1.php.net
21 OctoberThe UK's NCSC publishes an alert asking organisations to act immediately.NCSC
21 OctoberwatchTowr reports observing exploitation attempts against both CVEs in its honeypot network.watchTowr
22 OctoberNCSC updates its alert. NCSC-NL's public inventory of PHP-dependent products continues to be updated, with entries such as rebuilt Docker images on PHP 8.4.27.NCSC, NCSC-NL

What each organisation said

The PHP project described the flaws as remote code execution through out-of-memory corruption (CVE-2026-109618) and through stale global state (CVE-2026-109619). It said all PHP installations serving web requests are at risk, highest for Apache with mod_php, and that only updating is a complete fix. It also noted that PHP 8.2 reaches end of life on 31 December 2026.

The NCSC said the issue may allow attackers to run commands on any web server running PHP, and set out six steps: find every PHP installation, update, apply temporary mitigations if you can't, consider taking systems offline if you can't do either quickly, check systems you couldn't update for signs of compromise, and watch suppliers for updates.

Wiz, which found the flaws, described four memory-safety bugs grouped under the two CVEs, and said every PHP version released in the last decade is affected by at least one of them.

watchTowr reported exploitation attempts on 21 October and advised updating every PHP installation, restarting PHP workers, and restricting access to systems that can't be updated straight away.

What it means for a small business

For most small businesses, the work is short: confirm with your web host that PHP has been updated, keep an eye on the suppliers you rely on, and be wary of scam messages that use the news. Start with PHP2Shell: what small businesses need to do today.

A note on dates

You may see other dates quoted online. We list only dates published by the PHP project, the researchers, the NCSC and named security companies, and we'll correct this page if a primary source changes.

Questions people ask

When was PHP2Shell fixed?

On 21 October 2026, in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35.

Who discovered PHP2Shell?

Wiz Research. It says it found the first flaw on 19 August 2026 and reported the flaws to the PHP security team on 24 August 2026.

When was PHP2Shell announced?

php.net pre-announced a critical security release on 20 October 2026 and published the fixes and advisory on 21 October 2026.

Has PHP2Shell been exploited?

watchTowr reported seeing exploitation attempts against both flaws in its honeypot network on 21 October 2026. Exploitation attempts don't mean any particular website has been compromised.

Will this page be updated?

Yes. The "Updated" date at the top changes whenever we add something.

More on PHP2Shell

  • CVE-2026-109618 and CVE-2026-109619 explained in plain English
  • How to check which PHP version your website runs
  • Old PHP versions past end of life: why they matter now
  • When your suppliers go down

Sources

  • Upcoming critical PHP security release, 20 October 2026 (php.net)
  • PHP security advisory, 21 October 2026 (php.net)
  • Critical security issue affecting PHP (NCSC)
  • PHP2Shell research and timeline (Wiz)
  • PHP2Shell exploitation (watchTowr)
  • PHP2Shell software inventory (NCSC-NL)
  • The PHP developer who became the unsung hero of the internet, 25 October 2026 (BBC News)
  • What is PHP and why did it spark a global cyber-security scramble?, 22 October 2026 (BBC News)

Check your website free

See what your website shows the world in about a minute: a plain-language report, who should fix each thing, and a message to send them.

Check my website

Free to check

See what your website shows the world.

Check my website free
HackSpotby Amethyst Apps

Plain-language security checks for your website and the suppliers your business depends on.

HackSpot

  • How it works
  • What we check
  • Free check
  • Pricing

Resources

  • Guides
  • Insights
  • Supplier status

Help

  • About
  • Security
  • Contact us

Amethyst Apps

  • All apps
  • IndexStream
  • Partners

© 2026 Amethyst Apps. Built in the UK.

2G, Ingram House, 227 Ingram Street, Glasgow, G1 1DA, United Kingdom

PrivacyTermsCookiesSecuritySitemapPartners
EnglishEspañolFrançaisDeutschItalianoPortuguêsNederlandsPolskiSvenska日本語
HackSpot