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.
44% validated1,006 of 2,2727% before t=0
1,500 of 2,272 drawn
CVE-2026-70197
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 19m
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
20 of 1,249 entries
ETK-2026-1874Zero'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
4d 01h 02msince last run(AI 16m)Analysis: how long the AI spent reversing this signal.
cvss7.7awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−4.1dkevAttacks confirmed in the real world.
CVE-2026-107349ETK-2026-1872Zero'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
4d 01h 33msince last run(AI 50m)Analysis: how long the AI spent reversing this signal.
cvss7.5cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
CVE-2026-76655ETK-2026-1871Zero'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
2d 01h 04msince last run(AI 9m)Analysis: how long the AI spent reversing this signal.
cvss7.5cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
CVE-2026-96661ETK-2026-1867Zero'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
4d 03h 25msince last run(AI 37m)Analysis: how long the AI spent reversing this signal.
cvss7.5cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
CVE-2026-78193ETK-2026-1866Zero'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
4d 03h 19msince last run(AI 51m)Analysis: how long the AI spent reversing this signal.
cvss7.5cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
CVE-2026-100136ETK-2026-1858Zero'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
4d 06h 29msince last run(AI 36m)Analysis: how long the AI spent reversing this signal.
cvss7.5cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
CVE-2026-77206ETK-2026-1856Zero'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
4d 07h 05msince last run(AI 48m)Analysis: how long the AI spent reversing this signal.
cvss7.5cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
CVE-2026-77207ETK-2026-1855Zero'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
4d 05h 39msince last run(AI 2h 23m)Analysis: how long the AI spent reversing this signal.
cvss7.5cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
CVE-2026-105107ETK-2026-1849Zero'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
4d 08h 02msince last run(AI 45m)Analysis: how long the AI spent reversing this signal.
cvss7.6cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
ETK-2026-1848Zero'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
3d 08h 09msince last run(AI 13m)Analysis: how long the AI spent reversing this signal.
cvss7.5awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−6.6dkevAttacks confirmed in the real world.
CVE-2026-75608ETK-2026-1847Zero'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
4d 09h 03msince last run(AI 21m)Analysis: how long the AI spent reversing this signal.
cvss7.7cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−86dkevAttacks confirmed in the real world.
CVE-2026-110842ETK-2026-1846Zero'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
4d 09h 01msince last run(AI 33m)Analysis: how long the AI spent reversing this signal.
cvss7.7cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
CVE-2026-110845ETK-2026-1845Zero'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
4d 08h 57msince last run(AI 41m)Analysis: how long the AI spent reversing this signal.
cvss7.7cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
CVE-2026-57492ETK-2026-1842Zero'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
4d 09h 42msince last run(AI 8m)Analysis: how long the AI spent reversing this signal.
cvss7.4cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
CVE-2026-100353ETK-2026-1841Zero'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
4d 09h 38msince last run(AI 14m)Analysis: how long the AI spent reversing this signal.
cvss7.5cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
CVE-2026-73793ETK-2026-1839Zero'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
4d 09h 50msince last run(AI 9m)Analysis: how long the AI spent reversing this signal.
cvss7.9cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
CVE-2026-55103ETK-2026-1838Zero'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
3d 08h 52msince last run(AI 58m)Analysis: how long the AI spent reversing this signal.
cvss8.6cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
CVE-2026-96956ETK-2026-1834Zero'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
4d 09h 52msince last run(AI 49m)Analysis: how long the AI spent reversing this signal.
cvss8.0cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
CVE-2026-111854ETK-2026-1833Zero'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
1d 08h 20msince last run(AI 24m)Analysis: how long the AI spent reversing this signal.
cvss8.1cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
ETK-2026-1831Zero'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
3d 09h 56msince last run(AI 14m)Analysis: how long the AI spent reversing this signal.
cvss8.2awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.