← back to feed
ETK-2026-2874Zero's internal tracking ID, independent of the CVE number.

ETK-2026-2874Zero's internal tracking ID, independent of the CVE number.

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
ETK-2026-2874Zero's internal tracking ID, independent of the CVE number., no cve assigned
cvss9.0ethiack provisional
1h 44msince last run
37mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0hwaiting for further signals+1h01m
0
+2h
+3h

description

The available evidence identifies PHP as affected but does not specify impacted versions, deployment configurations, or the underlying bug class. It does not establish what an attacker can do or the conditions required for exploitation; defenders should treat PHP asset inventory and authoritative vendor guidance as the immediate basis for assessment.

mitigation

Inventory PHP installations and exposed PHP-backed services, then obtain and apply the vendor’s authoritative updates or configuration guidance for the affected release. Restrict unnecessary public access to PHP applications while confirming exposure.

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
37m
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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-10-28 13:50Z

this entry in the feed

GET /api/v1/feed/ETK-2026-2874

{
  "etk_id": "ETK-2026-2874",
  "cve_id": null,
  "display_id": "ETK-2026-2874",
  "ghsa_id": null,
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "PHP vulnerability with unconfirmed bug class",
  "summary": "The available evidence identifies PHP as affected but does not specify impacted versions, deployment configurations, or the underlying bug class. It does not establish what an attacker can do or the conditions required for exploitation; defenders should treat PHP asset inventory and authoritative vendor guidance as the immediate basis for assessment.",
  "mitigation": "Inventory PHP installations and exposed PHP-backed services, then obtain and apply the vendor’s authoritative updates or configuration guidance for the affected release. Restrict unnecessary public access to PHP applications while confirming exposure.",
  "vendor": "PHP",
  "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": 36.584804733333335,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-28T13:50:59+00:00",
      "days": -0.11423592255787036,
      "is_lower_bound": true,
      "measured_at": "2026-10-28T16:35:29.012493+00:00",
      "url": "https://www.bleepingcomputer.com/news/security/even-after-php2shell-blast-radius-matters-more-than-a-cvss-score/"
    }
  }
}

published 2026-10-28 14:15Z
last change 2026-10-28 16:08Z

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.