CVE-2026-109618

waiting for further signalsZero needs more public information before it can validate it.
no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
PHP security team PHP
ETK-2026-2243Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss9.0ethiack provisional
1h 40msince last run
6mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0hwaiting for further signals+3h31m
0
+1h
+2h
+3h
+4h
+5h

description

PHP deployments may be affected by two vulnerabilities for which emergency patches are being prepared. The available evidence does not disclose the vulnerability classes, affected versions, attacker impact, or conditions required for exploitation.

mitigation

Identify all deployed PHP versions and prepare to apply the emergency updates when released; verify the installed package and version afterward. Restrict public exposure of PHP-hosting services and isolate systems that cannot be updated promptly.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
6m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-20 20:56Z

this entry in the feed

GET /api/v1/feed/CVE-2026-109618

{
  "etk_id": "ETK-2026-2243",
  "cve_id": "CVE-2026-109618",
  "display_id": "CVE-2026-109618",
  "ghsa_id": null,
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "PHP flaws requiring emergency updates",
  "summary": "PHP deployments may be affected by two vulnerabilities for which emergency patches are being prepared. The available evidence does not disclose the vulnerability classes, affected versions, attacker impact, or conditions required for exploitation.",
  "mitigation": "Identify all deployed PHP versions and prepare to apply the emergency updates when released; verify the installed package and version afterward. Restrict public exposure of PHP-hosting services and isolate systems that cannot be updated promptly.",
  "vendor": "PHP security team",
  "product": "PHP",
  "affected": [],
  "cwes": null,
  "cvss_score": 9,
  "cvss_src": "ethiack_provisional",
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 6.09123545,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-20T20:56:43+00:00",
      "days": -0.2157883173263889,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T02:07:27.133621+00:00",
      "url": "https://www.bleepingcomputer.com/news/security/php-warns-admins-of-two-critical-flaws-emergency-patches-coming-tomorrow/"
    }
  }
}

published 2026-10-21 00:23Z
last change 2026-10-21 01:51Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.