validatingCVE-2026-5866312m
ETK-2026-1004waiting for further signals+1h 19mCVE-2026-107703check available+13mCVE-2026-107378waiting for further signals+15mCVE-2026-107376waiting for further signals+19mCVE-2026-103663check available+27mCVE-2026-107640check available+20mCVE-2026-105830check available+18mCVE-2026-92555waiting for further signals+1h 08mCVE-2026-105110waiting for further signals+9mCVE-2026-107450waiting for further signals+35m

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% validated1,006 of 2,2657% before t=0
1,500 of 2,265 drawn
CVE-2026-92798
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
+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).
15 of 454 entries
listcard
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 14h 21msince last run(AI 1h 19m)Analysis: how long the AI spent reversing this signal.
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−13dkevAttacks confirmed in the real world.cvss9.8
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.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+42mkevAttacks confirmed in the real world.cvss9.3
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 16h 33msince last run(AI 15m)Analysis: how long the AI spent reversing this signal.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−31dkevAttacks confirmed in the real world.cvss8.7
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 16h 35msince last run(AI 19m)Analysis: how long the AI spent reversing this signal.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−167dkevAttacks confirmed in the real world.cvss8.2
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.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+11dkevAttacks confirmed in the real world.cvss9.4
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.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+0mkevAttacks confirmed in the real world.cvss9.3
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.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−17dkevAttacks confirmed in the real world.cvss8.7
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 16h 43msince last run(AI 1h 08m)Analysis: how long the AI spent reversing this signal.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+6h05mkevAttacks confirmed in the real world.cvss9.1
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 01h 54msince last run(AI 9m)Analysis: how long the AI spent reversing this signal.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−36mkevAttacks confirmed in the real world.cvss9.3
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 02msince last run(AI 35m)Analysis: how long the AI spent reversing this signal.
cve.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.cvss8.1
CVE-2026-85097ETK-2026-948Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
8 Oct 2026 • Bricksforge <= 3.1.8.9
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+3.2dTTVTime-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.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+1.9dkevAttacks confirmed in the real world.−1dcvss9.8
ETK-2026-939Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
7 Oct 2026 • other:eneo < 2.2.0-rc.5
no check availablenot proven exploitable
13d 05h 05msince last run(AI 1h 00m)Analysis: how long the AI spent reversing this signal.
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−14dkevAttacks confirmed in the real world.cvss7.7
CVE-2026-106102ETK-2026-936Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
6 Oct 2026 • npm quasar <= 2.21.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.5dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 19m)Analysis: how long the AI spent reversing this signal.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−77dkevAttacks confirmed in the real world.cvss10.0
ETK-2026-921Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
7 Oct 2026 • go:github.com/stacklok/toolhive >= 0.13.0, < 0.51.4
no check availablenot proven exploitable
13d 09h 37msince last run(AI 35m)Analysis: how long the AI spent reversing this signal.
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−14dkevAttacks confirmed in the real world.cvss7.1
CVE-2026-76268ETK-2026-909Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
7 Oct 2026 • Splunk Enterprise >= 10.4, < 10.4.3; >= 10.2, < 10.2.7
no check availablenot proven exploitable
6d 14h 50msince last run(AI 1h 31m)Analysis: how long the AI spent reversing this signal.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+5.8dkevAttacks confirmed in the real world.cvss9.8