Failles critiques dans PHP : quelles versions mettre à jour et comment protéger ses serveurs

Failles critiques dans PHP : quelles versions mettre à jour et comment protéger ses serveurs

Promoted by curator@php.newsroom from the source watch (vault oq9gflln, read from its pack copy 7r83qic5), page be/news/blogdumoderateur/failles-critiques-php-versions-mettre-a-jour-comment-protege, snapshot 20261023T160435Z. Copied byte for byte; every file's sha256 is in captures/20261023T160435Z/provenance.json and was re-checked against the watch's own hashes.

What the page says

_Curator's reading of the capture._

Blog du Modérateur (French): which PHP versions to update and how to protect servers. CVE-2026-109618 and CVE-2026-109619 are rated 9.2 out of 10 on CVSS v4.0 and sit in PHP's engine, in memory handling, so any site on a vulnerable PHP version is exposed whatever its own code.

> se situent dans le moteur de PHP lui-même, au niveau de la gestion de la mémoire

_Curator's translation:_ "lie in PHP's engine itself, at the level of memory management"

_The watch reader's summary (researcher@php.newsroom, of its snapshot 20261022T181608Z, not necessarily this one):_ Blog du Modérateur explains which PHP versions to update and how. It cites CERT-FR's alert, GoDaddy's guidance and W3Techs version shares. It also reports the French Interior Ministry's preventive maintenance at ANSSI's request and ANSSI's count of PHP servers in France.

Why it is here

From the promotion queue (index/promote.json, priority 3): Mentions CVE-2026-109618/109619 or php2shell: "Failles critiques dans PHP : quelles versions mettre à jour et comment protéger ses serveurs". Selected mechanically, not read by a person. Text also matches compromise/breach terms: check for a named organisation or cause.

Capture notes

Language fr-FR. Nothing in the page addresses an AI or hides text from a reader.