Prototype F, the line: the editor's design of 25 October, built from the live data of release v0.18.2. Not the live site.The design notes →
PHPOctober 2026 the menu follows your role on the live site

Developing · data as of 24 October 2026, 16:05 UTC

Two serious security flaws in PHP, the software behind many of the world's websites

A fix came out on 21 October. Whoever runs a website needs to install it, and restart it.

Fixed in PHP 8.5.12, 8.4.27, 8.3.36, 8.2.35. An update only counts once the service restarts.

Target 8.5.12, 8.4.27, 8.3.36 or 8.2.35; restart every worker, rebuild images, verify with php -v inside the running container.

Is there a fix?
Yes
since 21 October
How serious?
Critical
both flaws, 9.2 of 10
Anyone broken into?
None named
millions of attempts
Government advice
Update
all 16 agencies agree

Three questions for your team

1

Do we know every system that runs PHP?

Websites, internal tools, suppliers, and the images we build from.

2

Is each one updated, and restarted?

Fixed in PHP 8.5.12, 8.4.27, 8.3.36, 8.2.35. An update only counts once the service restarts.

3

Who can take a system offline, and how fast?

Two US agencies say take it offline if it cannot be updated. Decide now who makes that call.

Does it touch you?

Two flaws were found in PHP itself, the engine that runs WordPress, Drupal, Wikipedia's software and millions of other sites. Either lets anyone on the internet, with no password, run commands on the

Not your phone or laptop: the flaw is on web servers. It affects organisations that run websites on PHP, and their visitors only indirectly. If you run a website, the question is whether PHP on its se

What to do

A fix has been available since 21 October. Organisations that run websites on PHP are installing it.

Every government cyber agency says: install the fix now. If you cannot, the US agencies say take the website offline; the UK puts that after temporary mitigations, and several European agencies say cu

Attackers are trying to use the flaws, in large numbers: millions of attempts by one internet security company's count. As of 16:05 UTC on 24 October, no named organisation has said it was broken into

Your next three actions

1

Patch internet-facing first.

mod_php, then FPM, then the rest. Restart every worker; rebuild every image.

2

Bound the known paths.

session.upload_progress off, low post_max_size, pm.max_requests on FPM. Each blocks a path; none is a fix.

3

Watch the process tree.

Alert on a PHP worker spawning a shell or a downloader. A clean access log proves nothing about the host.

Right now

A fix has been available since 21 October. Organisations that run websites on PHP are installing it.

Every government cyber agency says: install the fix now. If you cannot, the US agencies say take the website offline; the UK puts that after temporary mitigations, and several European agencies say cu

Attackers are trying to use the flaws, in large numbers: millions of attempts by one internet security company's count. As of 16:05 UTC on 24 October, no named organisation has said it was broken into

What nobody knows yet

Whether any website was actually broken into before it installed the fix.

Whether the fix is complete. A report on 21 October suggested it may not be; the PHP security team replied on the mailing list on 22 October, and this site will settle the question once that reply is

Who leaked the news on 20 October, and where.

Attack signals

2026-10-17 One exploit attempt against a MadPot honeypot from a commercial anonymisation network, four days before disclosure; 'it remains unclear how the actor

2026-10-17 One exploit attempt against a MadPot honeypot from an IP on a commercial anonymisation network, geolocated to Australia, four days before disclosure.

2026-10-20 to 21 'We observed attack traffic targeting our customers' after the leak, and attackers 'mutating the attack payload to try to bypass our protections'. No

The advice, now

Every government cyber agency says: install the fix now. If you cannot, the US agencies say take the website offline; the UK puts that after temporary mitigations, and several Euro

Attackers are trying to use the flaws, in large numbers: millions of attempts by one internet security company's count. As of 16:05 UTC on 24 October, no named organisation has sai

The spectrum

every agency, by what it says to do with a system you cannot patch
6 No offline advice
EU ENISA CSIRTs NetworkAU ASD's ACSCNZ NCSCNL NCSC-NLIT ACN / CSIRT ItaliaJP JPCERT/CC
2 Consider it, or after other steps
UK NCSCCH BACS
1 Restrict access
LV CERT.LV
3 Isolate from the internet
EU CERT-EUFR CERT-FRCA CCCS
2 Take it offline
US NSA CybersecurityUS CISA

Not readable from this capture environment: CCN-CERT, CNCS.

How sure are we?

70 facts

Fixed versions, and the settings until you are there

Fixed in8.5.12 · 8.4.27 · 8.3.36 · 8.2.35
memory_limit=-1, set where applications cannotRemoves the controllable memory-limit failure; an underlying allocation failure can still reach the vulnerable
A low post_max_size (8M without uploads, 32M wReduces exposure to specific attack paths; does not make an installation safe.
A container or cgroup memory limit as an availDo not use RLIMIT_AS or RLIMIT_DATA: they can cause the vulnerable allocation failure.
session.upload_progress.enabled=0 in php.ini, Blocks the confirmed session paths only. ini_set() and .user.ini are too late.

Which setups are exposed

Apache mod_php Unauthenticated RCE demonstrated over HTTP with default input and memory limits, before any application code runs.

PHP-FPM For CVE-2026-109618 the GitHub advisory says no complete FPM exploit has been demonstrated; the PHP Foundation blog says RCE was confirmed on FPM thro

php-cgi Listed by php.net among installations serving web requests.

Where the fix is

{'commit': '3584a98bda0f2c0d367255b046798b0d3a221a19', 'short': '3584a98bd', 'subject': 'Avoid state corruption via bailout', 'author': 'Arnaud Le Blanc', 'authored': '2026-10-18T15:26:39Z', 'committe

[{'layer': 'The language a site is written in (PHP code)', 'in_scope': False, 'text': "Not where the bug is. A site's own PHP code can be perfect; php2shell.com's phrase is that a 'Hello World' applic

Before you write: three things often got wrong

The numbers in the news, and how far each holds

70%Not stated. The headline is a restatement of the body's figure for websites.unverified
almost 70%The share of websites whose server-side language is PHP, as commonly published by web-technology surveys. Neither page names the survey.reported
about 30 millionNot stated.reported
2,608,039Hosts observed on the internet that expose PHP, as counted by one scanning vendor.reported
about 6,000Resources identified by the national CERT as potentially affected, in one country.reported
674Rows in the inventory: 206 marked Vulnerable, 46 Fix, 418 Investigation, 3 Not vulnerable, 1 without a status.confirmed

How it unfolded

2024An audit spots the out-of-memory weakness. Nobody can show it is exploitable, so it is left.
Aug 2026Three teams using AI turn it into working attacks within three weeks and report them to PHP.
20 OctThe secret leaks: the CVE numbers circulate two days early, with a wrong severity score.
21 OctPHP releases the fix a day ahead of plan. Firewall vendors already have rules live.
22 OctAgencies warn: update, or take systems offline. Sites go dark as a precaution.

Also contested

15 facts

The open questions

1

Whether any website was actually broken into before it installed the fix.

2

Whether the fix is complete. A report on 21 October suggested it may not be; the PHP secur

ity team replied on the mailing list on 22 October, and this site will settle the question once that reply is saved here. Separate

3

Who leaked the news on 20 October, and where.

The two bug classes

[{'step': 'Before the fix', 'text': "When a request pushed PHP past memory_limit, the allocator called zend_mm_safe_error, which raised a fatal error inside a zend_try and then called zend_bailout(): a C longjmp back to

What was shown

Apache mod_php Unauthenticated RCE demonstrated over HTTP with default input and memory limits, before any application code runs.

PHP-FPM For CVE-2026-109618 the GitHub advisory says no complete FPM exploit has been demonstrated; the PHP Foundation blog says RCE was confirmed o

That is the page for you.