PHP told users to prepare for a critical security release on October 21. Details come with the packages.
PHP's October 20 notice schedules a security release for October 21 at 14:00 UTC, for two flaws it rates 9.2. Fixed versions and technical details were not in that notice.
The short version
PHP's October 20, 2026 notice says a security release addressing two critical flaws, each rated 9.2 on CVSS v4.0, is scheduled for October 21 at 14:00 UTC, and that affected versions and fixed versions will be published with the release. NCSC and CERT-EU told operators to be ready to update.
A notice, not a changelog
On October 20, 2026 the PHP project posted an advance notice. The news archive says a security release is scheduled for Wednesday, October 21, 2026 at 14:00 UTC, that it addresses two critical vulnerabilities, and that both are rated CVSS v4.0 9.2. It tells every PHP user to prepare so they can upgrade as soon as the packages exist. It reserves an earlier release if details become public or if the project sees exploitation. Full details, affected versions, and fixed versions come with the release, not before.the advisory is the story.
The identifiers other advisories use
CERT-EU's advisory 2026-018, referring to the same notice, names the two flaws as CVE-2026-109618 and CVE-2026-109619. It says no technical details were public apart from the 9.2 scores, which it reads as indicating unauthenticated remote code execution. This page uses those identifiers because the advisory does. It does not add a method, a request shape, or a configuration key. PHP's own notice, in the text on php.net, did not need those identifiers to tell operators the clock.Chrome's warning is a product setting.
NCSC's list is preparation
The UK National Cyber Security Centre published its note on October 21. It repeats the schedule, as 15:00 British time, and says the release may come earlier. It asks organisations to find PHP across their estate, to watch internet-facing systems, to follow PHP's own guidance, to apply updates when they appear, and to watch vendors whose appliances bundle PHP. Where an immediate update is not possible, it says consider taking the system offline until it is mitigated. That is a readiness list. It is not a patch this page can point at.what a session cannot be.
What the notice withholds
The project says the affected versions and the fixed versions arrive with the packages. CERT-EU says it does not have technical details. A version string that circulated before the release, in outlets that were guessing the branch numbers, is not a number PHP had published in the notice these sources quote. This page will not print one. Operators who need the package read the project when the release exists. Asked directly, Did PHP name fixed version numbers? Not in the October 20 notice. It says full details, affected versions, and the fixed versions will be published with the release. A version number from a secondary guess is not this page's fact.the software desk.
Who is in scope
Anyone running PHP, especially on a network that accepts traffic from outside the organisation, is the population NCSC names first. Appliances and services that bundle PHP are in scope because NCSC says to ask those vendors too. A site that does not run PHP is outside the notice. End-of-life branches are a question the October 20 notice does not answer with a version list, so this page does not invent which old branches are uncovered.Bullhorn says access is restored.
Ars is the wire, these three are the record
The software and privacy wires carried Ars Technica's account of the warning, and the security wire carried a SANS diary headline that uses the same two identifiers. This page's sources are the project notice, NCSC, and CERT-EU, because those are the documents that set the schedule and the score without a procedure. A diary that goes further is not copied here. Asked directly, What score did PHP assign? Both flaws are rated CVSS v4.0 9.2, which PHP calls critical. CERT-EU repeats that score. The notice does not include a breakdown of the score.four stable kernels on Wednesday.
A scheduled release is the fact
As of the notices in these sources, the public record is a clock, a severity, and an instruction to be ready. It is not a list of fixed tarballs. If the project ships at 14:00 UTC, the versions in that shipment are a later document. If it ships earlier under the clause it reserved, that shipment is the document. This page does not pretend the packages were already named. Asked directly, Who is NCSC speaking to? UK organisations that run PHP. It says to identify those systems, starting with internet-facing ones, and to apply the updates when they exist. Where that cannot be done immediately, it says consider taking the system offline until it is mitigated.Linux 7.4 closes files inline.
What stays on the record
October 20 notice. Release scheduled October 21, 2026, 14:00 UTC. Two flaws, each CVSS v4.0 9.2. CERT-EU's identifiers CVE-2026-109618 and CVE-2026-109619, with no technical detail attached. NCSC's preparation list. No fixed version numbers in the notice. The short answer this page will stand on is this: PHP's October 20, 2026 notice says a security release addressing two critical flaws, each rated 9.2 on CVSS v4.0, is scheduled for October 21 at 14:00 UTC, and that affected versions and fixed versions will be published with the release. NCSC and CERT-EU told operators to be ready to update.Futureweb.
What would move the row
The release announcement that names affected versions and fixed packages would replace this schedule. Evidence the project says it has seen exploitation would matter because the notice reserved an earlier ship date for that case. Neither document is the October 20 post. Asked directly, When is the release scheduled? PHP says Wednesday, October 21, 2026, at 14:00 UTC. NCSC states the same moment as 15:00 British time. The project also says it may publish earlier if details leak or if it sees exploitation.the privacy desk.
Sources
The reports this brief is filing. Futureweb did not republish them.
Questions
When is the release scheduled?
PHP says Wednesday, October 21, 2026, at 14:00 UTC. NCSC states the same moment as 15:00 British time. The project also says it may publish earlier if details leak or if it sees exploitation.
What score did PHP assign?
Both flaws are rated CVSS v4.0 9.2, which PHP calls critical. CERT-EU repeats that score. The notice does not include a breakdown of the score.
Did PHP name fixed version numbers?
Not in the October 20 notice. It says full details, affected versions, and the fixed versions will be published with the release. A version number from a secondary guess is not this page's fact.
Who is NCSC speaking to?
UK organisations that run PHP. It says to identify those systems, starting with internet-facing ones, and to apply the updates when they exist. Where that cannot be done immediately, it says consider taking the system offline until it is mitigated.
Does CERT-EU publish a method?
No. Its advisory says no technical details were public, apart from the scores, and it tells organisations to prepare to patch and, if they cannot, to isolate internet-facing applications from public networks.