ETK-2026-4657Zero'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.
MEV-Boost relay code
ETK-2026-4657Zero's internal tracking ID, independent of the CVE number., no cve assigned
1d 11h 50msince last run
25mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
waiting for further signals−35h50mtrigger signal −35h28m
−24h
−12h
0

description

MEV-Boost relay code may allow a malicious participant in the block-building workflow to obtain block contents before the expected validator-signing step is completed. This can enable manipulation of transactions in a targeted block when the attacker can participate as a validator or otherwise interact with the affected relay workflow.

mitigation

Use only trusted, maintained relay operators and restrict validator use of relays that cannot enforce signed-block validation before releasing payload data. Monitor relay and validator activity for unexpected payload requests or block-submission behavior; the available evidence names no fixed release.

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
25m
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-11-17 09:44Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4657",
  "cve_id": null,
  "display_id": "ETK-2026-4657",
  "ghsa_id": null,
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Premature block payload release in MEV-Boost relay code",
  "summary": "MEV-Boost relay code may allow a malicious participant in the block-building workflow to obtain block contents before the expected validator-signing step is completed. This can enable manipulation of transactions in a targeted block when the attacker can participate as a validator or otherwise interact with the affected relay workflow.",
  "mitigation": "Use only trusted, maintained relay operators and restrict validator use of relays that cannot enforce signed-block validation before releasing payload data. Monitor relay and validator activity for unexpected payload requests or block-submission behavior; the available evidence names no fixed release.",
  "vendor": null,
  "product": "MEV-Boost relay code",
  "affected": [],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 25.011141883333334,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-11-17T09:44:22+00:00",
      "days": -1.4779682689930556,
      "is_lower_bound": true,
      "measured_at": "2026-11-18T21:12:38.506679+00:00",
      "url": "https://www.bleepingcomputer.com/news/security/court-clears-brothers-of-25-million-ethereum-crypto-heist-charges/"
    }
  }
}

published 2026-11-17 09:54Z
last change 2026-11-18 21:09Z

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.