CSI Atlas

2026-018: Critical Vulnerabilities in PHP

INT-b5195c57daacunknownunknownRevision 5

Vulnerabilities and exploitation

Claims and certainty

  1. What the record states

    On 20 October 2026, the PHP project announced an upcoming security release addressing two critical vulnerabilities in PHP. Public reports indicated that these vulnerabilities could lead to remote code execution (RCE).<br>

    The PHP team released the fixes today, 21 October 2026 at 13:30 UTC, in PHP versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Both vulnerabilities can allow unauthenticated remote code execution. Technical details are now being discussed publicly, and initial proofs of concept (PoCs) have begun to circulate. This raises the likelihood that attackers are already exploiting the vulnerabilities.<br>

    [New] On 23 October, PHP disclosed a new RCE vulnerability. However, it affects only web applications configured in an unusual way, and PHP considers it an unlikely risk. PHP will not issue an out-of-band release for this vulnerability. Instead, organisations are advised to apply mitigation to fully protect from this RCE vector.<br>

    CERT-EU advises organisations to patch affected assets immediately. Where that is not feasible, organisations should consider isolating internet-facing applications from public networks until a fix is applied and verified.<br>

    Link to this claim

  2. How certain it is

    This record summarizes the cited public sources. Its uncertainties remain explicit.

    This is a report by the cited official source. Automated checks verify source identity, retained bytes, exact wording and date. They do not independently verify exploitation, victim impact or attribution.

    Link to this claim

Record details

Record facts.
FieldValue
Event classVulnerabilities and exploitation
Jurisdictionunknown
Claim typereported
Our assessmentmoderate
Publisher typeofficial (descriptive, not a truth score)
What the source isOfficial publisher. It states the body position, not an independent verification.
Source reliabilitynot separately scored by this publication
Who assigned the assessmentThis publication
Review routeAutomated source check
Revision5
Record updated15 Nov 2026, 00:10 IST

Dates

Date roles for this record.
Date kindStatedPrecisionRoleNote
Event dateunknownunknowneventthe source did not state a date
Source publication date23 Oct 2026daypublicationCERT-EU security advisories
Record updated15 Nov 2026, 00:10 ISTdayrecord clockthe time this publication last updated the record; not a source date

Evidence

Sources cited by this record.
PublisherRelationPublishedSource
CERT-EU security advisoriessupports23 Oct 2026Open source

CERT-EU security advisories Quotation: unclear. Attribution: unstated. Redistribution: unclear. No reuse statement recorded in this register yet.

Retained originals

Original versions retained for this record.
SourceRevisionHow it was keptRetainedSHA-256
CERT-EU security advisories5source copy retained with the record15 Nov 2026, 00:10 ISTe96932b7023757ba7b0bffe7a5a715776cd5de9aa1960d5ccbf9c4734de833aa

What this record does not hold

A gap is stated in public words. It is not counted as evidence.

No quotation shown

The publisher terms recorded for this source do not clearly allow quotation, so no quotation is reproduced. The source link is shown instead.

Cite this record

A citation is bound to this version.
FieldValue
Version5
Canonical link/record/INT-b5195c57daac
Correction pointerCorrection history for this record
Permitted useCite this record with its version and link. Quotation is allowed only where the publisher terms shown on this record allow it. Do not redistribute this record in bulk.

Origins 1, analysis 0, carriers 0, not recorded 0. Depth 1: Direct sources only. This publication does not trace an origin behind a cited source.

N 1 record ยท as of 19 Nov 2026, 01:52 IST