validatingCVE-2026-764735m
ETK-2026-389waiting for further signals+28mCVE-2026-41510check available+15mETK-2026-387waiting for further signalsCVE-2026-73802check available+1h 14mETK-2026-385waiting for further signals+44mETK-2026-384waiting for further signals+25mETK-2026-383waiting for further signals+20mCVE-2026-84411check available+26mCVE-2026-82041waiting for further signals+1h 23mCVE-2026-104019waiting for further signals+18m

The clock starts when a 0-day surfaces. How long before attackers strike?

Attackers often exploit new vulnerabilities before defenders can react, sometimes before the vulnerability even gets a public ID (a CVE).
Ethiack Zero is a live tracker of that race between attackers and defenders.

Zero is Ethiack’s public record of emerging 0-days. It turns early signals and patches into a working proof of exploit, then publishes how fast it validates each vulnerability (time-to-validateTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.) next to how fast attackers exploited it (time-to-exploitTime-to-Exploit: how long after public disclosure attackers take to exploit a vulnerability in the wild.).

explore live feed
Vulnerability Time-to-validate (TTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.)live
How fast Ethiack Zero proves a vulnerability is exploitable. Each dot is one vulnerability. The further left, the earlier it was confirmed. The centre line is the moment the vulnerability was fully disclosed on cve.org.
timelinedistribution
44% validated1,016 of 2,3007% before t=0
1,500 of 2,300 drawn
CVE-2026-92798
TTV+5h
−8d−6d−4d−2dt=0The moment cve.org publishes the CVE in full.+4d+8d+12d+16d+20d+24d
validated before cve.org publicationvalidated after cve.org publicationvalidatingvalidated but not publishedConfirmed, but cve.org has not published a CVE yet, so there is no t = 0. It sits at how long ago we confirmed it, as if the CVE were published now, and moves left until it is.
Vulnerability Timeline
From first warning to first attack. The typical journey of a new vulnerability, using median times. Time zero is the official disclosure of the vulnerability on cve.org.
step 1
signal ingested
0m
A new vulnerability surfaces
step 2
validating
3h 15m
How fast Zero starts validating it
step 3
validated
+4h 52m
How fast we confirm if it's exploitable
step 4
t = 0, CVE published
t = 0
t=0: the CVE goes public
step 5
Attack confirmed (KEV)
2d
How fast an attacker exploits this in the wild

Exploit live feed

Live Feed
Every vulnerability Ethiack Zero is tracking, right now. Each card is one vulnerability and shows where it stands. New ones appear as they surface.
Methodology
all
STATUS
validatingZero is analyzing and reversing it now.validatedZero produced an exploit or a check.waiting for further signalsZero needs more public information before it can validate it.
OUTCOMES
check availableZero validated a working check for it.proven exploitableZero has validated a full working exploit.
PUBLIC SIGNALS
cve confirmedOfficially announced by cve.org.kevAttacks confirmed in the real world.public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
15 of 2,300 entries
listcard
ETK-2026-389Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
2 Oct 2026 • go:github.com/siyuan-note/siyuan/kernel < 0.0.0-20260813142806-dd2778b70d02
no check availablenot proven exploitable
18d 19h 23msince last run(AI 28m)Analysis: how long the AI spent reversing this signal.
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−19dkevAttacks confirmed in the real world.cvss8.2
CVE-2026-41510ETK-2026-388Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
2 Oct 2026 • go:github.com/corazawaf/coraza/v3 >= 3.0.0, < 3.8.1
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
−9.8dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 15m)Analysis: how long the AI spent reversing this signal.
cve.org+9.8dpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−6.0dkevAttacks confirmed in the real world.cvss7.2
ETK-2026-387Zero's internal tracking ID, independent of the CVE number.
withdrawn
2 Oct 2026 • go:github.com/corazawaf/coraza/v3 >= 3.0.0, < 3.8.1
no check availablenot proven exploitable
11d 20h 33msince last run
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.cvss7.5
CVE-2026-73802ETK-2026-386Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
2 Oct 2026 • go:gitea.com/gitea/runner < 1.0.9-0.20260731160927-34bfa1915022
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+1.1dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 1h 14m)Analysis: how long the AI spent reversing this signal.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.cvss9.9
ETK-2026-385Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
2 Oct 2026 • npm:trigger.dev < 4.5.2
no check availablenot proven exploitable
17d 18h 59msince last run(AI 44m)Analysis: how long the AI spent reversing this signal.
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−19dkevAttacks confirmed in the real world.cvss7.1
ETK-2026-384Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
2 Oct 2026 • npm:trigger.dev <= 4.5.5
no check availablenot proven exploitable
18d 20h 05msince last run(AI 25m)Analysis: how long the AI spent reversing this signal.
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−19dkevAttacks confirmed in the real world.cvss8.1
ETK-2026-383Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
2 Oct 2026 • npm:trigger.dev < 4.5.4
no check availablenot proven exploitable
18d 20h 17msince last run(AI 20m)Analysis: how long the AI spent reversing this signal.
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−19dkevAttacks confirmed in the real world.cvss9.2
CVE-2026-84411ETK-2026-382Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
2 Oct 2026 • MikroTik RouterOS < 7.24
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+1h22mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 26m)Analysis: how long the AI spent reversing this signal.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+7.7dkevAttacks confirmed in the real world.cvss9.3
CVE-2026-82041ETK-2026-379Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
2 Oct 2026 • UTMStack < 11.2.16
no check availablenot proven exploitable
18d 20h 31msince last run(AI 1h 23m)Analysis: how long the AI spent reversing this signal.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.cvss9.9
CVE-2026-104019ETK-2026-378Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
2 Oct 2026 • AWS sagemaker-distribution 2.14.x: < 2.14.12; 3.9.x: < 3.9.12; 4.0.x: < 4.0.11; 4.1.x: < 4.1.11; 4.2.x: < 4.2.8; 4.3.x: < 4.3.5; 4.4.x: < 4.4.3; 2.8.x - 2.13.x
no check availablenot proven exploitable
18d 21h 45msince last run(AI 18m)Analysis: how long the AI spent reversing this signal.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.cvss9.3
CVE-2026-82039ETK-2026-377Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
2 Oct 2026 • UTMStack < 11.2.16
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+2h56mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 1h 16m)Analysis: how long the AI spent reversing this signal.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.cvss8.7
CVE-2026-111767ETK-2026-376Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
2 Oct 2026 • npm:@modelcontextprotocol/sdk >= 1.24.0, < 1.32.0
no check availablenot proven exploitable
1d 01h 02msince last run(AI 13m)Analysis: how long the AI spent reversing this signal.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.cvss8.6
ETK-2026-375Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
2 Oct 2026 • npm:trigger.dev < 4.5.2
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
−19dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.and counting(AI 38m)Analysis: how long the AI spent reversing this signal.
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−19dkevAttacks confirmed in the real world.cvss7.7
CVE-2026-82042ETK-2026-374Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
2 Oct 2026 • UTMStack < 11.2.16
no check availablenot proven exploitable
18d 18h 30msince last run(AI 53m)Analysis: how long the AI spent reversing this signal.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.cvss9.3
CVE-2026-104873ETK-2026-373Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
2 Oct 2026 • langchain-ai langgraph >= 0.1.45, <= 0.4.3
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+3.2dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 15m)Analysis: how long the AI spent reversing this signal.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.cvss7.6