validatingCVE-2026-1070842m
ETK-2026-44waiting for further signals+14mCVE-2026-86104check available+1h 46mCVE-2026-86131waiting for further signals+15mCVE-2026-102792waiting for further signals+10mCVE-2026-103043check available+7mCVE-2026-103042waiting for further signals+13mCVE-2026-103040waiting for further signals+52mCVE-2026-103041waiting for further signals+26mCVE-2023-54400kev listed+19mCVE-2026-102600waiting for further signals+16m

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. The curve shows how many were confirmed at each point in time; a dot is one still validating or waiting for its CVE. The further left, the earlier it was confirmed. The centre line is the moment the vulnerability was fully disclosed on cve.org.
timelinedistribution
44% validated989 of 2,2357% before t=0
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
+5h 05m
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,200 entries
listcard
ETK-2026-44Zero'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 • npm:adm-zip <= 0.6.0
no check availablenot proven exploitable
5d 02h 52msince last run(AI 14m)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).−21dkevAttacks confirmed in the real world.
CVE-2026-86104ETK-2026-43Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
29 Sep 2026 • WatchGuard Fireware OS >= 2026.3, < 2026.3.2; >= 2025.0, < 2026.2.3; >= 12.0, < 12.12.3; >= 12.0, < 12.5.21
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+17dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 1h 46m)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.
CVE-2026-86131ETK-2026-42Zero'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 • WatchGuard Fireware OS >= 2026.3, < 2026.3.2; >= 2025.0, < 2026.2.3; >= 12.0, < 12.12.3; >= 12.0, < 12.5.21
no check availablenot proven exploitable
2d 19h 36msince last run(AI 15m)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-102792ETK-2026-38Zero'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 • Ziroom ZHOME A0101 1.0.1.0
no check availablenot proven exploitable
4d 07h 12msince last run(AI 10m)Analysis: how long the AI spent reversing this signal.
cvss9.4cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+0mkevAttacks confirmed in the real world.
CVE-2026-103043ETK-2026-37Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
29 Sep 2026 • alexcorvi anchorme <= 3.0.8
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+17dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 7m)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.
CVE-2026-103042ETK-2026-36Zero'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 • ModelTC LightLLM <= 1.2.0
no check availablenot proven exploitable
5d 10h 16msince last run(AI 13m)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.
CVE-2026-103040ETK-2026-35Zero'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 • ModelTC LightLLM <= 1.2.0
no check availablenot proven exploitable
3d 09h 00msince last run(AI 52m)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-103041ETK-2026-34Zero'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 • ModelTC LightLLM <= 1.2.0
no check availablenot proven exploitable
3d 14h 29msince last run(AI 26m)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-2023-54400ETK-2026-33Zero'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 • Fumasoft Fumeng Cloud *
no check availablenot proven exploitable
19d 04h 20msince last run(AI 19m)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.0d
CVE-2026-102600ETK-2026-32Zero'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 • npm:@socket.io/cluster-engine <0.1.1
no check availablenot proven exploitable
9h 44msince 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-56271ETK-2026-31Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
21 Sep 2026 • FlowiseAI Flowise <=3.0.13
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+79dTTVTime-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.
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.+71d
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 05h 28msince 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
15h 27msince 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 22h 40msince 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 04h 06msince 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 04h 18msince 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.