How early could an attacker get control of a website?
Your login is one piece of a much larger system.
Reveal the discovery
Before the website’s own login code started.
PHP is software that builds web pages on a server, the computer that sends pages to your browser. In the demonstrated attack, researchers made PHP run their own instructions before the website checked a password.
The demonstration used Apache with mod_php, one way to run PHP. The attacker had the same permissions as the server program handling the request. That did not automatically give them control of the whole computer.
Look beneath the login
The login is the part you see. PHP handles the request underneath it.
The flaw, in three steps.
Read straight through, or select a step to see it inside.
1. A request reaches PHP.
A request is a message sent to a server. The attacker sends a specially made one, and PHP starts setting up the data to handle it.
2. PHP runs out of working room.
Memory is PHP’s temporary workspace. If it fills up at the wrong moment, setup can stop halfway through, leaving data unfinished.
3. Cleanup can run the wrong instructions.
PHP tried to clean up after the failure. It could use the unfinished data to decide which instructions to run next. Researchers exploited that mistake to make PHP run their instructions.
This illustrates the out-of-memory flaw demonstrated against Apache with mod_php. Other server setups have different attack conditions.
Why the login couldn’t help.
The attack happened while PHP was preparing the request. The website’s own code, including its login check, hadn’t started yet.
The PHP project released fixes on October 21, 2026. Email-alias service addy.io chose to take its website and web app offline while patching; its email delivery kept working.
A demonstrated attack does not mean every affected website was hacked. Other ways of running PHP have different attack conditions.