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).−4h32mkevAttacks 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
47msince last run
34mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −10h41mpublic poc−4h32mwaiting for further signals−0h47m
−10h
−8h
−6h
−2h
0

description

PHP is the affected component, but the available evidence does not identify the flaw class, affected function, or affected versions. The evidence also does not establish what an attacker can do or what access or configuration precondition is required.

mitigation

Monitor official PHP security announcements and apply the emergency updates as soon as the relevant releases are published. Reduce exposure by limiting public access to PHP-backed services where operationally feasible until affected versions are identified.

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.
–
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
34m
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).
−4h32m
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-10-20 20:56Z
  2. 2026-10-20 20:56Z
  3. 2026-10-21 06:18Z

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": "Reported vulnerability in PHP security team PHP",
  "summary": "PHP is the affected component, but the available evidence does not identify the flaw class, affected function, or affected versions. The evidence also does not establish what an attacker can do or what access or configuration precondition is required.",
  "mitigation": "Monitor official PHP security announcements and apply the emergency updates as soon as the relevant releases are published. Reduce exposure by limiting public access to PHP-backed services where operationally feasible until affected versions are identified.",
  "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": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 34.39083506666667,
  "t0_at": null,
  "signals": {
    "public_poc": {
      "at": "2026-10-21T03:06:03+00:00",
      "days": -0.18893601418981482,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T07:38:07.107489+00:00",
      "url": "https://github.com/Zer061/CVE-2026-109618"
    },
    "trigger_signal": {
      "at": "2026-10-20T20:56:43+00:00",
      "days": -0.4454174956712963,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T07:38:07.107489+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 07:37Z

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.