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% validated987 of 2,2257% before t=0
1,500 of 2,225 drawn
CVE-2026-78164
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 20m
How fast Zero starts validating it
step 3
validated
+5h 04m
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 31 entries
CVE-2026-112247ETK-2026-2086Zero'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 05h 45msince last run(AI 29m)Analysis: how long the AI spent reversing this signal.
cvss5.3cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+0mkevAttacks confirmed in the real world.0d
CVE-2026-96951ETK-2026-2022Zero'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
2h 37msince last run(AI 13m)Analysis: how long the AI spent reversing this signal.
cvss8.8cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.+9m
CVE-2026-96652ETK-2026-2021Zero'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 21h 56msince last run(AI 23m)Analysis: how long the AI spent reversing this signal.
cvss5.3cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+23dkevAttacks confirmed in the real world.+25d
CVE-2026-103671ETK-2026-1986Zero'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 10h 29msince last run(AI 51m)Analysis: how long the AI spent reversing this signal.
cvss5.3cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.0d
CVE-2026-39781ETK-2026-1983Zero'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 10h 30msince last run(AI 37m)Analysis: how long the AI spent reversing this signal.
cvss7.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.+9d
CVE-2026-74920ETK-2026-1982Zero'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 11h 07msince last run(AI 19m)Analysis: how long the AI spent reversing this signal.
cvss7.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.0d
CVE-2026-15382ETK-2026-1953Zero'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 15h 28msince last run(AI 1h 06m)Analysis: how long the AI spent reversing this signal.
cvss6.5cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+0mkevAttacks confirmed in the real world.+77d
CVE-2026-110447ETK-2026-1539Zero'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 07h 22msince last run(AI 35m)Analysis: how long the AI spent reversing this signal.
cvss9.2cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+16h55mkevAttacks confirmed in the real world.0d
CVE-2026-19949ETK-2026-1526Zero'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
6d 23h 20msince last run(AI 20m)Analysis: how long the AI spent reversing this signal.
cvss8.8cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+8.9dkevAttacks confirmed in the real world.+49d
CVE-2026-90817ETK-2026-1523Zero'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
5d 23h 08msince last run(AI 10m)Analysis: how long the AI spent reversing this signal.
cvss9.8cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+18h02mkevAttacks confirmed in the real world.+17d
CVE-2026-15748ETK-2026-1518Zero'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
6d 23h 29msince last run(AI 47m)Analysis: how long the AI spent reversing this signal.
cvss9.8cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+9h13mkevAttacks confirmed in the real world.+56d
CVE-2026-102255ETK-2026-1331Zero'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
8d 17h 29msince last run(AI 15m)Analysis: how long the AI spent reversing this signal.
cvss10.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.0d
CVE-2026-85103ETK-2026-1271Zero'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
9d 03h 32msince last run(AI 8m)Analysis: how long the AI spent reversing this signal.
cvss9.8cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.+16d
CVE-2026-97670ETK-2026-1135Zero'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
8d 11h 41msince last run(AI 31m)Analysis: how long the AI spent reversing this signal.
cvss9.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.−1d
CVE-2026-97359ETK-2026-601Zero'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
15d 23h 35msince last run(AI 1h 53m)Analysis: how long the AI spent reversing this signal.
cvss10.0cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+0mkevAttacks confirmed in the real world.+9d
CVE-2026-88779ETK-2026-525Zero'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
14d 15h 15msince last run(AI 18m)Analysis: how long the AI spent reversing this signal.
cvss8.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.−2d
CVE-2026-5430ETK-2026-506Zero'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
16d 22h 09msince last run(AI 30m)Analysis: how long the AI spent reversing this signal.
cvss10.0cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+51dkevAttacks confirmed in the real world.+40d
CVE-2024-58385ETK-2026-505Zero'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
17d 04h 03msince last run(AI 25m)Analysis: how long the AI spent reversing this signal.
cvss9.8cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+0mkevAttacks confirmed in the real world.0d
CVE-2026-76460ETK-2026-502Zero'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
17d 05h 36msince last run(AI 12m)Analysis: how long the AI spent reversing this signal.
cvss10.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.−2h02m
CVE-2026-86124ETK-2026-498Zero'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
17d 03h 51msince last run(AI 49m)Analysis: how long the AI spent reversing this signal.
cvss9.8cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.+13d