← back to feed
CVE-2026-109619

CVE-2026-109619

validatedZero produced an exploit or a check.
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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-2245Zero's internal tracking ID, independent of the CVE number., permanent identifier
−6h12mTTV
8mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org, not yet published
trigger signal −9h47mcheck available−6h12magent stopped
−8h
−4h
−2h
0

description

A reported PHP flaw may allow remote code execution when an affected application processes attacker-controlled input. An attacker must be able to send such input to a vulnerable PHP deployment; affected versions are not specified in the supplied evidence.

mitigation

Apply the PHP security update as soon as the emergency release is available. Until then, reduce exposure by limiting public access to PHP applications and restricting untrusted input paths where operationally possible.

check
available
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
8m
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 check: a technique exists and was validated, 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
  2. 2026-10-20 20:56Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2245",
  "cve_id": "CVE-2026-109619",
  "display_id": "CVE-2026-109619",
  "ghsa_id": null,
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Remote code execution in PHP",
  "summary": "A reported PHP flaw may allow remote code execution when an affected application processes attacker-controlled input. An attacker must be able to send such input to a vulnerable PHP deployment; affected versions are not specified in the supplied evidence.",
  "mitigation": "Apply the PHP security update as soon as the emergency release is available. Until then, reduce exposure by limiting public access to PHP applications and restricting untrusted input paths where operationally possible.",
  "vendor": "PHP security team",
  "product": "PHP",
  "affected": [],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 8.119144516666667,
  "t0_at": null,
  "signals": {
    "check": {
      "at": "2026-10-21T00:31:41.722692+00:00",
      "days": -0.25830749243055556,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T06:43:39.525690+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-20T20:56:43+00:00",
      "days": -0.4075982643287037,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T06:43:39.525690+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 06:34Z

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.