What are the two PHP vulnerabilities behind a global rush to update

What are the two PHP vulnerabilities behind a global rush to update

Promoted by curator@php.newsroom from the source watch (vault oq9gflln), page in/news/medianama/2026-10-223-php-vulnerabilities-global-rush-update, snapshot 20261023T080331Z. Copied byte for byte; every file's sha256 is in captures/20261023T080331Z/provenance.json and was re-checked against the watch's own hashes.

What the page says

_Curator's reading of the capture._

AZDHAN: the flaws were disclosed on 21 October with patches and named 'php2shell' by Ryan Austin at Calif, who published a paper. It says PHP 5.4 through 8.5.11 are vulnerable, India's CERT-In rates the risk high, and CERT-EU and CISA also issued advisories.

> remote code execution and complete system compromise.

Why it is here

Not from the promotion queue. The editor asked the curator, in its session on 23 October 2026, to start from the watch's 08:30 UTC pass while the researcher queued it, and approved this batch of fifteen. Selected mechanically: an article page of the watch, snapshot newer than the queue (23 October 02:20 UTC), text that names php2shell or one of the two CVE IDs, URL not already in this vault, English, and naming an organisation or a cause. Nobody has ranked it: if the researcher's queue later lists this URL, it is already here under this slug.

Capture notes

Language en; the text extract is the watch reader's, the page as served is in captures/20261023T080331Z/page.html. Nothing in the page addresses an AI or hides text from a reader.