validatingCVE-2026-11200017m
ETK-2026-1072waiting for further signals+10mETK-2026-1069waiting for further signals+8mCVE-2026-94503check available+24mCVE-2026-104635waiting for further signals+15mETK-2026-1042waiting for further signals+19mCVE-2026-107362check available+27mCVE-2026-107375waiting for further signals+17mETK-2026-1030check available+11mCVE-2026-107406waiting for further signals+12mCVE-2026-107722waiting for further signals+10m

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% validated1,006 of 2,2687% 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 20m
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).
20 of 454 entries
listcard
ETK-2026-1072Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
9 Oct 2026 • npm:@rsdoctor/utils <1.6.5
no check availablenot proven exploitable
12d 00h 22msince last run(AI 10m)Analysis: how long the AI spent reversing this signal.
cvss8.1awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−12dkevAttacks confirmed in the real world.
ETK-2026-1069Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
9 Oct 2026 • go:github.com/siyuan-note/siyuan >= 3.5.4, <= 3.8.6
no check availablenot proven exploitable
11d 00h 48msince last run(AI 8m)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).−12dkevAttacks confirmed in the real world.
CVE-2026-94503ETK-2026-1066Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
9 Oct 2026 • PX-lab Zombify <= 1.7.7
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+1h30mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 24m)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).+18h54mkevAttacks confirmed in the real world.−5d
CVE-2026-104635ETK-2026-1058Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
9 Oct 2026 • elixir-protobuf protobuf >= 0.8.0, <= 0.17.0
no check availablenot proven exploitable
11d 10h 57msince last run(AI 15m)Analysis: how long the AI spent reversing this signal.
cvss8.2cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−39mkevAttacks confirmed in the real world.
ETK-2026-1042Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
8 Oct 2026 • rust:tari_state_tree <= 0.43.0
no check availablenot proven exploitable
12d 07h 46msince last run(AI 19m)Analysis: how long the AI spent reversing this signal.
cvss8.8awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−13dkevAttacks confirmed in the real world.
CVE-2026-107362ETK-2026-1038Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
30 Sep 2026 • CISA Malcolm <= 26.08.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.6dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 27m)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).−8.0dkevAttacks confirmed in the real world.
CVE-2026-107375ETK-2026-1032Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
8 Oct 2026 • npm:generator-jhipster >= 7.0.0, < 9.4.0
no check availablenot proven exploitable
12d 09h 12msince last run(AI 17m)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).+4mkevAttacks confirmed in the real world.
ETK-2026-1030Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
9 Oct 2026 • uptime-kuma <=2.5.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.
−12dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.and counting(AI 11m)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).−12dkevAttacks confirmed in the real world.
CVE-2026-107406ETK-2026-1026Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
8 Oct 2026 • NetScaler ADC < 14.1-73.46; < 13.1-64.29; >= 0, < 14.1-73.46 FIPS; >= 0, < 13.1.37.283 FIPS
no check availablenot proven exploitable
11d 13h 55msince last run(AI 12m)Analysis: how long the AI spent reversing this signal.
cvss9.5cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+11h16mkevAttacks confirmed in the real world.
CVE-2026-107722ETK-2026-1020Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
8 Oct 2026 • npm:fast-jwt >= 6.2.0, <= 6.2.4
no check availablenot proven exploitable
12d 13h 01msince 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).+12mkevAttacks confirmed in the real world.
ETK-2026-1004Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
8 Oct 2026 • go:github.com/julien040/anyquery <= 0.5.0
no check availablenot proven exploitable
12d 15h 18msince last run(AI 1h 19m)Analysis: how long the AI spent reversing this signal.
cvss9.8awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−13dkevAttacks confirmed in the real world.
CVE-2026-107703ETK-2026-1003Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
8 Oct 2026 • enmaso @enmaso/node-convert <= 1.0.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.
+1h27mTTVTime-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.
cvss9.3cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+42mkevAttacks confirmed in the real world.
CVE-2026-107378ETK-2026-996Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
8 Oct 2026 • Kozea CairoSVG <= 2.9.0
no check availablenot proven exploitable
12d 17h 29msince last run(AI 15m)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).−31dkevAttacks confirmed in the real world.
CVE-2026-107376ETK-2026-995Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
8 Oct 2026 • webonyx graphql-php <= 15.32.2
no check availablenot proven exploitable
12d 17h 32msince last run(AI 19m)Analysis: how long the AI spent reversing this signal.
cvss8.2cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−167dkevAttacks confirmed in the real world.
CVE-2026-103663ETK-2026-992Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
8 Oct 2026 • Ollama >= 0.34.2, < 0.35.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.
+4h17mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 27m)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).+11dkevAttacks confirmed in the real world.
CVE-2026-107640ETK-2026-983Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
8 Oct 2026 • Integrics Enswitch >= 3.13, <= 4.4
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.2dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 20m)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).+0mkevAttacks confirmed in the real world.
CVE-2026-105830ETK-2026-982Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
8 Oct 2026 • thephpleague commonmark >= 2.0.0, <= 2.10.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.
+1h14mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(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).−17dkevAttacks confirmed in the real world.
CVE-2026-92555ETK-2026-969Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
8 Oct 2026 • AKIN Software Computer Import-Export Industry and Trade Co. Ltd. AKINSOFT WOLVOX Control Panel >= 26.02.25, < 26.02.26
no check availablenot proven exploitable
12d 17h 40msince last run(AI 1h 08m)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).+6h05mkevAttacks confirmed in the real world.
CVE-2026-105110ETK-2026-960Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
8 Oct 2026 • Iskratel Innbox
no check availablenot proven exploitable
13d 02h 51msince last run(AI 9m)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).−36mkevAttacks confirmed in the real world.
CVE-2026-107450ETK-2026-953Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
8 Oct 2026 • stumpapp Stump <= 0.1.10
no check availablenot proven exploitable
13d 03h 59msince last run(AI 35m)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).−2.6dkevAttacks confirmed in the real world.