validatingCVE-2026-11087310m
ETK-2026-2219waiting for further signals+11mCVE-2026-111758check available+8mETK-2026-2212waiting for further signals+14mETK-2026-2211waiting for further signals+31mETK-2026-2210check available+31mETK-2026-2206waiting for further signals+9mCVE-2026-113802waiting for further signals+1h 29mCVE-2026-113506waiting for further signals+25mETK-2026-2196waiting for further signals+13mETK-2026-2195waiting for further signals+15m

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% validated984 of 2,2137% before t=0
1,500 of 2,213 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 17m
How fast Zero starts validating it
step 3
validated
+5h 03m
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 444 entries
listcard
ETK-2026-2219Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
20 Oct 2026 • pip:numcodecs >= 0.17.0, < 0.17.1; >= 0.16.0, < 0.16.6; >= 0.1.0, < 0.15.2
no check availablenot proven exploitable
5h 18msince last run(AI 11m)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).−6h28mkevAttacks confirmed in the real world.
CVE-2026-111758ETK-2026-2218Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
20 Oct 2026 • npm markdown-it >= 14.1.0, < 14.3.3; >= 15.0.0, < 15.0.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.
+18mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 8m)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).+0mkevAttacks confirmed in the real world.
ETK-2026-2212Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
19 Oct 2026 • rust:static-web-server <= 3.0.0-beta.1
no check availablenot proven exploitable
6h 03msince 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).−1.5dkevAttacks confirmed in the real world.
ETK-2026-2211Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
17 Oct 2026 • maven:org.yamcs:yamcs-core <= 5.13.6
no check availablenot proven exploitable
5h 46msince last run(AI 31m)Analysis: how long the AI spent reversing this signal.
cvss8.5awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−3.2dkevAttacks confirmed in the real world.
ETK-2026-2210Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
16 Oct 2026 • rust:lopdf < 0.42.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.
−5h11mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.and counting(AI 31m)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).−4.2dkevAttacks confirmed in the real world.
ETK-2026-2206Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
20 Oct 2026 • npm:happy-dom >= 17.0.0, <= 21.0.3
no check availablenot proven exploitable
7h 14msince last run(AI 9m)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).−7h16mkevAttacks confirmed in the real world.
CVE-2026-113802ETK-2026-2204Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
20 Oct 2026 • Wavlink WL-WN530BE1-A M30BE1_V251117
no check availablenot proven exploitable
6h 21msince last run(AI 1h 29m)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-113506ETK-2026-2201Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
20 Oct 2026 • aaPanel 8.0; 8.1; 8.2; 8.3; 8.4; 8.5; 8.6; 8.7; 8.8; 8.9; 8.10; 8.11; 8.12; 8.13; 8.14; 8.15; 8.16; 8.17; 8.18; 8.19; 8.20; 8.21; 8.22; 8.23; 8.24; 8.25.0
no check availablenot proven exploitable
7h 53msince last run(AI 25m)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).−27dkevAttacks confirmed in the real world.
ETK-2026-2196Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
19 Oct 2026 • composer:enshrined/svg-sanitize >= 0.11.0, <= 1.0.0
no check availablenot proven exploitable
8h 34msince last run(AI 13m)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).−1.6dkevAttacks confirmed in the real world.
ETK-2026-2195Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
19 Oct 2026 • composer:enshrined/svg-sanitize >= 0.5.3, <= 1.0.0
no check availablenot proven exploitable
8h 34msince last run(AI 15m)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).−1.6dkevAttacks confirmed in the real world.
CVE-2026-113390ETK-2026-2188Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
20 Oct 2026 • DrayTek Vigor2960 1.5.1.6 Revision 8218
no check availablenot proven exploitable
6h 29msince last run(AI 1h 32m)Analysis: how long the AI spent reversing this signal.
cvss9.9cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+4h05mkevAttacks confirmed in the real world.
CVE-2026-113391ETK-2026-2183Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
20 Oct 2026 • DrayTek Vigor2960 1.5.1.6 Revision 8218
no check availablenot proven exploitable
10h 06msince last run(AI 35m)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).+1h17mkevAttacks confirmed in the real world.
CVE-2026-85250ETK-2026-2176Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
19 Oct 2026 • Apache Software Foundation Apache Camel >= 4.0.0, < 4.18.5; >= 4.19.0, < 4.22.1
no check availablenot proven exploitable
12h 30msince last run(AI 19m)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).+3h11mkevAttacks confirmed in the real world.
CVE-2026-113389ETK-2026-2175Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
20 Oct 2026 • DrayTek Vigor2960 1.5.1.6 Revision 8218
no check availablenot proven exploitable
9h 52msince last run(AI 1h 19m)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).+1h00mkevAttacks confirmed in the real world.
CVE-2026-113358ETK-2026-2158Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
20 Oct 2026 • lavalite cms <= 10.1.2
no check availablenot proven exploitable
14h 14msince last run(AI 55m)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).+0mkevAttacks confirmed in the real world.
CVE-2026-102756ETK-2026-2139Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
14 Oct 2026 • maven:io.dataease <2.10.26
no check availablenot proven exploitable
17h 14msince last run(AI 42m)Analysis: how long the AI spent reversing this signal.
cvss5.1cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−76dkevAttacks confirmed in the real world.
CVE-2026-102755ETK-2026-2136Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
14 Oct 2026 • maven:io.dataease <2.10.26
no check availablenot proven exploitable
17h 35msince last run(AI 43m)Analysis: how long the AI spent reversing this signal.
cvss5.1cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−76dkevAttacks confirmed in the real world.
CVE-2026-100351ETK-2026-2133Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
15 Oct 2026 • go github.com/getkin/kin-openapi v0.144.0 through v0.146.0
no check availablenot proven exploitable
18h 35msince last run(AI 8m)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).−58dkevAttacks confirmed in the real world.
CVE-2026-104141ETK-2026-2129Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
14 Oct 2026 • maven:io.dataease <2.10.26
no check availablenot proven exploitable
18h 10msince last run(AI 48m)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).−76dkevAttacks confirmed in the real world.
CVE-2026-107083ETK-2026-2121Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
19 Oct 2026 • SLiMS Bulian n/a
no check availablenot proven exploitable
19h 16msince last run(AI 41m)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).−1.9dkevAttacks confirmed in the real world.