validatingETK-2026-22745m
CVE-2026-77423waiting for further signals+24mCVE-2026-84409waiting for further signals+1h 00mCVE-2026-71379check available+16mCVE-2026-71971check available+1h 59mCVE-2026-74220waiting for further signals+19mCVE-2026-74221waiting for further signals+32mCVE-2026-74222waiting for further signals+23mCVE-2026-91191check available+21mCVE-2026-102266check available+13mCVE-2026-102267waiting for further signals+12m

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% 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
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).
20 of 2,028 entries
listcard
CVE-2026-77423ETK-2026-30Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
23 Sep 2026 • maven:org.jline:jline-builtins < 4.3.1; >= 3.0.0, < 3.30.15
no check availablenot proven exploitable
9d 03h 51msince last run(AI 24m)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).−85dkevAttacks confirmed in the real world.
CVE-2026-84409ETK-2026-29Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
29 Sep 2026 • Lantronix G520 Series 2.6.0.4R6 stable
no check availablenot proven exploitable
13h 49msince last run(AI 1h 00m)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-71379ETK-2026-28Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
29 Sep 2026 • Toptech Systems TMS7 7.6.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.
+15dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 16m)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.
CVE-2026-71971ETK-2026-27Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
29 Sep 2026 • u-boot < 2026.10-rc3
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+2h51mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 1h 59m)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.
CVE-2026-74220ETK-2026-26Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
29 Sep 2026 • u-boot < 2026.10-rc5
no check availablenot proven exploitable
5d 21h 03msince last run(AI 19m)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.
CVE-2026-74221ETK-2026-25Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
29 Sep 2026 • u-boot < 2026.10-rc5
no check availablenot proven exploitable
6d 02h 29msince last run(AI 32m)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.
CVE-2026-74222ETK-2026-24Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
29 Sep 2026 • u-boot < 2026.10-rc5
no check availablenot proven exploitable
6d 02h 41msince last run(AI 23m)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.
CVE-2026-91191ETK-2026-23Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
29 Sep 2026 • Lantronix G520 Series 2.6.0.4R6 stable
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+1h16mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(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).kevAttacks confirmed in the real world.
CVE-2026-102266ETK-2026-22Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
28 Sep 2026 • pip:PyJWT 2.13.0
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 13m)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).+1.1dkevAttacks confirmed in the real world.
CVE-2026-102267ETK-2026-21Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
28 Sep 2026 • pip:PyJWT <= 2.13.0
no check availablenot proven exploitable
3d 08h 25msince last run(AI 12m)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-102271ETK-2026-19Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
28 Sep 2026 • pip:PyJWT 2.13.0
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.0dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 13m)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).+1.1dkevAttacks confirmed in the real world.
CVE-2026-102272ETK-2026-18Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
28 Sep 2026 • pip:PyJWT 2.13.0
no check availablenot proven exploitable
5d 20h 37msince last run(AI 10m)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-91776ETK-2026-17Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
23 Sep 2026 • maven:com.fasterxml.jackson.core:jackson-databind >= 2.0.0, <= 2.18.10; >= 2.19.0, <= 2.21.6; >= 2.22.0, <= 2.22.2; >= 3.0.0, <= 3.1.6; >= 3.2.0, <= 3.2.2
no check availablenot proven exploitable
20d 05h 30msince last run(AI 16m)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-91777ETK-2026-16Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
23 Sep 2026 • maven:com.fasterxml.jackson.core:jackson-databind >= 2.5.0, <= 2.18.10; >= 2.19.0, <= 2.21.6; >= 2.22.0, <= 2.22.2; >= 3.0.0, <= 3.1.6; >= 3.2.0, <= 3.2.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.
+6.8dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 16m)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-102253ETK-2026-15Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
29 Sep 2026 • esnet iperf3 >= 3.14, < 3.22
no check availablenot proven exploitable
12d 01h 40msince last run(AI 20m)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).+7.9dkevAttacks confirmed in the real world.
CVE-2026-102273ETK-2026-14Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
28 Sep 2026 • pip:PyJWT = 2.13.0
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.0dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 12m)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-100291ETK-2026-12Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
29 Sep 2026 • Anjvision YSSD-RTMP-H5 Version 3.3.2.4 build 2024-12-26
no check availablenot proven exploitable
5d 14h 44msince last run(AI 17m)Analysis: how long the AI spent reversing this signal.
cvss9.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.
CVE-2026-53988ETK-2026-11Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
29 Sep 2026 • Finsys dockhand < 1.0.40
no check availablenot proven exploitable
6d 21h 03msince last run(AI 18m)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).kevAttacks confirmed in the real world.
CVE-2026-102876ETK-2026-10Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
29 Sep 2026 • surrealdb < 3.3.0
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+36mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 13m)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-65660ETK-2026-9Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
25 Sep 2026 • Microsoft SharePoint >= 16.0.0, < 16.0.5565.1001; >= 16.0.0, < 16.0.10417.20198; >= 16.0.0, < 16.0.19725.20522
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+51dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 29m)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).+45dkevAttacks confirmed in the real world.+44d