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

CVE-2026-109618 and CVE-2026-109619 explained in plain English

The two PHP2Shell flaws without jargon: what goes wrong inside PHP, who is at risk, how serious it is and which PHP versions fix it.

By HackSpot team (Amethyst Apps) · October 23, 2026 · 4 min read

HackSpot: CVE-2026-109618 and CVE-2026-109619 explained in plain English

The short version: CVE-2026-109618 and CVE-2026-109619 are two critical flaws in PHP, fixed on 21 October 2026 and together known as PHP2Shell. Both can let an attacker on the internet run their own commands on a web server without logging in. The fix is to update PHP to 8.5.12, 8.4.27, 8.3.36 or 8.2.35 (or newer). If your website runs PHP, check what it shows for free and ask your host to confirm.

The two flaws at a glance

CVE-2026-109618CVE-2026-109619
PHP's own nameRemote code execution via out-of-memory corruptionRemote code execution via stale global state
Severity (PHP project)Critical, CVSS v4.0 9.2Critical, CVSS v4.0 9.2
Login needed?NoNo
Fixed in8.2.35, 8.3.36, 8.4.27, 8.5.128.2.35, 8.3.36, 8.4.27, 8.5.12

What goes wrong, without the jargon

A web server running PHP handles thousands of visits. For speed, the same PHP "worker" handles one visit after another, tidying up between them.

CVE-2026-109618 is about what happens when PHP runs out of memory part-way through setting up a visit. The PHP advisory explains that running out of memory can interrupt PHP while it's only half-way through preparing the request's data, and the clean-up step can then treat that half-prepared data as if it were valid. A carefully crafted request can turn that confusion into control.

CVE-2026-109619 is about leftovers. Some of PHP's internal notes about a visit can outlive the memory they point to. If a visit is cut short (for example by a fatal error), the tidy-up can be skipped, and the next visit handled by the same worker may use those stale notes. The advisory names two confirmed paths: session upload progress (a PHP feature that is switched on by default) and, on PHP 8.5, a setting called fatal_error_backtraces.

In both cases the result can be memory being read or overwritten in ways PHP never intended. The advisories say this can lead to the attacker running code with the web server's permissions.

Who is at risk

The PHP advisory says: all PHP installations serving web requests, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. It considers the risk highest for mod_php, where it demonstrated an attack that works before any of the website's own code runs. The flaws are in PHP itself, so a well-written website on an unpatched PHP can still be exposed.

How serious is it?

Both flaws are rated critical (9.2 out of 10 on the CVSS v4.0 scale) by the PHP project. The UK's National Cyber Security Centre (NCSC) asked organisations to act straight away. watchTowr, a security company, reported seeing exploitation attempts against both flaws in its honeypot network on 21 October 2026, the day the fixes came out.

What fixes it

  • Updating PHP to 8.5.12, 8.4.27, 8.3.36 or 8.2.35, or a newer release in the same branch, then restarting every PHP worker. This is the only complete fix.
  • Older branches (8.1, 8.0, 7.4): the PHP project published minimal source backports for people who build PHP themselves, and some Linux distributions and long-term support vendors ship their own fixed packages. There's no new official release for these branches.

The temporary measures, and their limits

For people who can't update straight away, the PHP project published settings that reduce exposure to specific attack paths, such as limiting how much data a single upload request can send and switching off session upload progress. The PHP project is clear that these do not make an installation safe; only an update does. They're also server settings, so for most small businesses they're your host's job, not something to change yourself.

Questions people ask

What does "remote code execution" mean?

It means someone on the internet could make your web server run commands of their choosing, for example to plant malicious files, steal data or send spam, without needing a password.

Are older PHP versions affected?

Yes. The advisories list every release before 8.2.35, 8.3.36, 8.4.27 and 8.5.12 as affected, and Wiz, which found the flaws, says every PHP version released in the last decade is affected by at least one of them. Branches 8.1 and older get no new official release.

Does a firewall protect me?

Some web application firewall providers published protective rules, which can help while you update. They don't replace updating PHP.

Is my website hacked if it runs an affected version?

Not necessarily. Being affected means the flaw could be used; it doesn't mean it has been. If you're worried, ask your host to check for signs of compromise.

Where can I check my site?

Run a free HackSpot check. It shows whether your site reveals a PHP version and what that suggests, in plain English.

More on PHP2Shell

  • PHP2Shell: what small businesses need to do today
  • PHP2Shell timeline: what happened and when
  • What to ask your web host (email template)
  • What is PHP2Shell? (guide)

Sources

  • PHP security advisory, 21 October 2026 (php.net)
  • GitHub security advisory GHSA-w8hw-w9fx-j79w, CVE-2026-109618 (PHP project)
  • GitHub security advisory GHSA-6wmf-4rv5-p3rp, CVE-2026-109619 (PHP project)
  • Critical security issue affecting PHP (NCSC)
  • PHP2Shell research (Wiz)
  • PHP2Shell exploitation (watchTowr)

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