Threat+Constellation
Live— UTC

Execution · NO — NOT EXECUTED

PUBLIC RECORD

PHP 2026 — Vulnerability Discovery and Institutional Response

Public record of CVE-2026-109618 and CVE-2026-109619 (PHP2Shell). Facts below are limited to independently retrieved primary and secondary sources. Organizational response times are not part of this record. Honeypot attempts are not production compromise.

CVE-2026-109618 · CVE-2026-109619 · attack evidence ATTEMPTED_EXPLOITATION

What is verified
CVE identifiers, affected version bounds, fixed versions, 21 Oct 2026 publication date, unauthenticated RCE class.
What remains unknown
Exact discovery time, vendor-notification instant, production compromise, and any named organizational response.

Discovery Clock

Date-bounded intervals are not confirmed measurements. Time of day is NOT ESTABLISHED for the 17 October MadPot attempt.

  • Discovery to vendor notification

    discoveryAt → vendorNotificationAt · INCOMPLETE

    NOT ESTABLISHED

  • Discovery to public disclosure

    discoveryAt → publicDisclosureAt · INCOMPLETE

    NOT ESTABLISHED

  • Discovery to patch availability

    discoveryAt → patchAvailableAt · INCOMPLETE

    NOT ESTABLISHED

  • First observed exploitation relative to disclosure

    firstObservedExploitationAt → publicDisclosureAt · mixed precision

    ≈4d 0h (date precision · time of day NOT ESTABLISHED)

  • Disclosure to patch availability

    publicDisclosureAt → patchAvailableAt · mixed precision

    ≈0 (date precision · time of day NOT ESTABLISHED)

Evidence register

  • VERIFIED_PUBLIC_FACT · OBSERVED · PUBLIC_SOURCE · PUBLIC

    CVE-2026-109618 and CVE-2026-109619 are published identifiers for critical unauthenticated RCE classes in PHP.

    Supported statement: CVE-2026-109618 record retrieved 24 Oct 2026: OOM/longjmp path can lead to remote code execution; CVSS 9.2 CRITICAL; affected 8.2 before 8.2.35, 8.3 before 8.3.36, 8.4 before 8.4.27, 8.5 before 8.5.12. oss-security 21 Oct 2026 announces CVE-2026-109619 with the same version bounds.

  • VERIFIED_PUBLIC_FACT · OBSERVED · PUBLIC_SOURCE · PUBLIC

    Fixed upstream versions are PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35.

    Supported statement: php.net archive 2026: 'PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 fix two critical vulnerabilities that can allow unauthenticated remote code execution.' Corroborated by PHP Foundation, CVE product status, oss-security, CISA, CERT-EU, and AWS bulletin.

  • VERIFIED_PUBLIC_FACT · OBSERVED · PUBLIC_SOURCE · PUBLIC

    The security releases were published on 21 October 2026.

    Supported statement: PHP archive announces 8.5.12 / 8.4.27 / 8.3.36 / 8.2.35 as released. PHP Foundation post is dated 21 Oct 2026: 'Earlier today, the PHP project released PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35.'

  • VERIFIED_PUBLIC_FACT · OBSERVED · PUBLIC_SOURCE · PUBLIC

    On 20 October 2026 PHP gave advance notice of a 21 October 14:00 UTC security release.

    Supported statement: php.net archive: 'The PHP security team would like to give advance notice of an upcoming security release. It is scheduled for Wednesday, 21 October 2026 at 14:00 UTC.'

  • SOURCE_STATED · STATED · PUBLIC_SOURCE · PUBLIC

    PHP Foundation and AWS state the coordinated release / embargo lift as 21 October 2026, 14:00 UTC. CERT-EU states 13:30 UTC. Exact minute remains SOURCE_STATED.

    Supported statement: PHP Foundation: the project 'moved the release from October 22nd, 14:00 UTC, to October 21st, 14:00 UTC.' AWS MadPot: 'The actual release of the embargo window was 2026-10-21 1400 UTC.' CERT-EU: 'The PHP team released the fixes today, 21 October 2026 at 13:30 UTC.' The 30-minute discrepancy is preserved, not averaged.

  • VERIFIED_PUBLIC_FACT · OBSERVED · PUBLIC_SOURCE · PUBLIC

    Both CVEs can allow unauthenticated remote code execution. Exploitability depends on configuration and request path; not every deployment is proven exploitable in the same way.

    Supported statement: PHP Foundation: the releases 'fix two critical vulnerabilities that, under the right conditions, allow an unauthenticated attacker to execute code on servers running PHP.' oss-security: 'Unauthenticated RCE has been demonstrated against Apache mod_php and PHP-FPM. Exploitability depends on the affected state, configuration, and application behavior.'

  • VERIFIED_PUBLIC_FACT · OBSERVED · PUBLIC_SOURCE · PUBLIC

    Public advisories describe the RCE class as unauthenticated. That is not a claim that every PHP host was reachable or exploited.

    Supported statement: CISA: the vulnerabilities 'allow for unauthenticated remote code execution in PHP.' AWS bulletin: 'accessible remotely by an actor without authentication over the internet-to-customer-application boundary.'

  • SOURCE_STATED · STATED · PUBLIC_SOURCE · PUBLIC

    CISA stated it had not observed successful exploitation in the wild as of the alert, including the 23 October update. That is CISA's observation, not a global proof of absence.

    Supported statement: CISA alert, last revised 23 Oct 2026: 'While CISA has not observed successful exploitation of these vulnerabilities in the wild as of the time of publication, they pose a risk to organizations if left unpatched.'

  • SOURCE_STATED · STATED · PUBLIC_SOURCE · PUBLIC

    CISA and CERT-EU state that PHP installations serving web requests are at risk. 'At risk' is not 'affected and compromised.'

    Supported statement: CISA: 'The vulnerabilities affect all PHP installations serving web requests, including Apache with mod_php … PHP-FPM, php-cgi, FrankenPHP and LiteSpeed.' CERT-EU: 'Every PHP installation that serves web requests is at risk.' Neither source reports that all PHP deployments were compromised.

  • SOURCE_STATED · STATED · PUBLIC_SOURCE · PUBLIC

    AWS reports a PHP2Shell exploitation attempt dated 17 October 2026 against MadPot, before public disclosure. AWS also states it is unclear whether attempts would have succeeded on real-world systems.

    Supported statement: AWS Security Blog, 21 Oct 2026: 'Amazon Threat Intelligence identified a PHP2Shell exploitation attempt dating to Oct. 17, 2026, in MadPot telemetry, four days before public disclosure.' Later: 'Technical analysis is ongoing, and it’s unclear if any of these attempts would have succeeded in real-world systems.' Classified ATTEMPTED_EXPLOITATION, not CONFIRMED_EXPLOITATION or CONFIRMED_COMPROMISE.

  • SOURCE_STATED · STATED · PUBLIC_SOURCE · PUBLIC

    AWS reports additional exploitation attempts against MadPot and, after embargo lift, 'broad exploitation attempts in the wild.' Attempts are not confirmed compromise of production systems.

    Supported statement: AWS: from 2026-10-21 0200 UTC to 0800 UTC, additional attempts targeted MadPot. After 1400 UTC embargo lift, 'PHP2Shell is now seeing broad exploitation attempts in the wild.' AWS also writes 'compromise may predate the advisory' as a lesson, not as a confirmed production incident.

  • SOURCE_STATED · STATED · PUBLIC_SOURCE · PUBLIC

    OpenAI states Calif identified a critical flaw using GPT-5.6 Sol, and that Wiz independently discovered and reported both vulnerabilities. That is OpenAI's account, not independently proven exclusive discovery.

    Supported statement: OpenAI, 21 Oct 2026: 'Calif identified a critical flaw using GPT‑5.6 Sol as part of our Patch the Planet initiative, with Wiz also independently discovering and reporting both vulnerabilities.' PHP Foundation corroborates independent reports from Calif (11 Aug), OpenAI, and Wiz (24 Aug), and notes AI tools were used while 'a person makes every call.'

  • SOURCE_STATED · STATED · PUBLIC_SOURCE · PUBLIC

    PHP Foundation states Calif reported unconditional RCE on 11 August 2026; OpenAI independently reported the same root cause; Wiz reported further vectors on 24 August.

    Supported statement: PHP Foundation: 'On August 11th, researcher Ryan A at Calif reported an unconditional remote code execution… OpenAI independently reported the same root cause, followed by further attack vectors from OpenAI on September 18th and from Wiz on August 24th.'

  • UNVERIFIED · EXCLUDE · OBSERVATORY_STRUCTURE · PUBLIC

    Every PHP installation worldwide was vulnerable in the same way and was compromised.

    Supported statement: Excluded. oss-security: exploitability depends on state, configuration, and application behavior. No retrieved source states that all PHP deployments were compromised.

  • UNVERIFIED · EXCLUDE · OBSERVATORY_STRUCTURE · PUBLIC

    AI independently discovered every vulnerability without human or parallel research.

    Supported statement: Excluded. PHP Foundation credits Calif, OpenAI, Wiz, and earlier 2024 internal OOM work. OpenAI's 'frontier AI found these vulnerabilities before attackers did' remains SOURCE_STATED, not a verified exclusive-cause claim.

  • UNVERIFIED · VERIFY · SYSTEM_INFERENCE · PUBLIC

    An exact discovery timestamp for either CVE.

    Supported statement: Not established. PHP Foundation gives report dates (11 Aug Calif; later OpenAI/Wiz) without a timezone-aware discovery instant. discoveryAt remains null.

  • UNVERIFIED · VERIFY · SYSTEM_INFERENCE · PUBLIC

    A named production organization was confirmed compromised via PHP2Shell.

    Supported statement: Not established in retrieved public sources. CISA reports no observed successful exploitation in the wild as of 23 Oct 2026. AWS honeypot telemetry is ATTEMPTED_EXPLOITATION.

Citations

Institutional decision friction

PHP Foundation statements describe the PHP Project. They are not conclusions about unnamed operators, and they do not establish that websites were breached. AWS MadPot remains ATTEMPTED_EXPLOITATION.

PUBLIC_NAMED · VENDOR_KNOWLEDGE · PUBLIC

PHP Project / PHP Foundation

Known Risk Dwell
≈70d–71d (bounded · time of day NOT ESTABLISHED)
Known Risk Dwell: confirmed awareness of a specific risk by a defined institution to a documented disposition. Disposition is not necessarily remediation. Public disclosure is not substituted for awareness.
Disposition
MITIGATION_COMPLETED
Unresolved Exposure
NOT ESTABLISHED
Public Disclosure Age
2d

Documented reasons, source-stated reasons, research hypotheses, and unknown causes remain separate. Elapsed time is not a cause. See methodology.

  • Risk awareness to acknowledgement

    RISK_SIGNAL_RECEIVED → RISK_ACKNOWLEDGED · INCOMPLETE

    NOT ESTABLISHED

  • Acknowledgement to assessment

    RISK_ACKNOWLEDGED → IMPACT_ASSESSMENT_STARTED · INCOMPLETE

    NOT ESTABLISHED

  • Assessment to decision request

    IMPACT_ASSESSMENT_COMPLETED → DECISION_REQUESTED · INCOMPLETE

    NOT ESTABLISHED

  • Decision request to authorization

    DECISION_REQUESTED → DECISION_AUTHORIZED · INCOMPLETE

    NOT ESTABLISHED

  • Authorization to mitigation start

    DECISION_AUTHORIZED → MITIGATION_STARTED · INCOMPLETE

    NOT ESTABLISHED

  • Mitigation start to completion

    MITIGATION_STARTED → MITIGATION_COMPLETED · date precision

    ≈71d 0h (date precision · time of day NOT ESTABLISHED)

Source-stated / documented

  • AUTHORITY_AMBIGUITY · SOURCE_STATED

    PHP Foundation states that a consensus-based security-team process stalled and restarted work on a fix over months. This is a SOURCE_STATED account of the PHP Project, not a finding about unrelated organizations, and not a negligence verdict.

  • RESOURCE_CONSTRAINT · SOURCE_STATED

    PHP Foundation attributes delay in part to lack of resources and few engineers with deep engine knowledge. SOURCE_STATED. Elapsed time alone is not used as proof of this factor.

  • COMPATIBILITY_RISK · SOURCE_STATED

    PHP Foundation states competing fix approaches risked compatibility breaks, new denial-of-service, or third-party extension changes.

  • COORDINATED_DISCLOSURE_DEPENDENCY · SOURCE_STATED

    Release timing was moved after a leak so distributors could package a fix. Chainguard is stated to have published patched images before the embargo lift. SOURCE_STATED.

Research hypotheses

None recorded.

Unknown causes

  • UNKNOWN · UNKNOWN_CAUSE

    Causes of any operator-side delay at unnamed organizations are UNKNOWN. Public knowledge of the CVE is not evidence that a given website owner knew, deferred, or was negligent.

Governance questions · research fields, not permissions

  • Who owns the risk?

    PHP security team / PHP Foundation for upstream php-src. Operator ownership for deployments is NOT ESTABLISHED. · STATED

  • Who may authorize mitigation?

    NOT ESTABLISHED · VERIFY

  • Who validates the evidence?

    NOT ESTABLISHED · VERIFY

  • Who approves production changes?

    NOT ESTABLISHED · VERIFY

  • Who determines acceptable downtime?

    NOT ESTABLISHED · VERIFY

  • Who verifies recovery?

    NOT ESTABLISHED · VERIFY

  • Who may reopen a risk decision?

    NOT ESTABLISHED · VERIFY

SYNTHETIC — NOT REAL-WORLD OBSERVATION · php-2026-synthetic-org

SYNTHETIC — Illustrative institutional response to PHP 2026

SYNTHETIC — NOT REAL-WORLD OBSERVATION. Organizational timestamps are modelled to demonstrate the institutional clock. They are not measurements of any named organization. Public CVE facts remain on the separate public record. Intervals calculated from this record are not observed metrics.

Boundary HOLD · Execution NO — NOT_EXECUTED

Synthetic intervals are demonstration values. They are not observed metrics and do not authorize production action.

SYNTHETIC · ORGANIZATION_CONFIRMED_KNOWLEDGE · SYNTHETIC

SYNTHETIC operator — research fixture (not a real organization)

Known Risk Dwell
≈2d–3d (bounded · time of day NOT ESTABLISHED) · SYNTHETIC · not an observed metric
Known Risk Dwell: confirmed awareness of a specific risk by a defined institution to a documented disposition. Disposition is not necessarily remediation. Public disclosure is not substituted for awareness.
Disposition
MITIGATION_COMPLETED
Unresolved Exposure
NOT ESTABLISHED
Public Disclosure Age
2d · SYNTHETIC · not an observed metric