validatingCVE-2026-1096180m
CVE-2026-62679check available+30mCVE-2026-58390waiting for further signals+16mCVE-2026-100349waiting for further signals+16mCVE-2026-59774check available+<1mCVE-2026-110958waiting for further signals+21mCVE-2026-57155check available+53mCVE-2026-102469waiting for further signals+29mCVE-2026-55683check available+27mCVE-2026-55680proven exploitable+29mCVE-2026-55684check available+14m

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% validated994 of 2,2477% before t=0
1,500 of 2,247 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 22m
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 451 entries
listcard
CVE-2026-62679ETK-2026-1698Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
15 Oct 2026 • LycheeOrg Lychee <= 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.
+1h20mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 30m)Analysis: how long the AI spent reversing this signal.
cvss8.9cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−111dkevAttacks confirmed in the real world.
CVE-2026-58390ETK-2026-1695Zero'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 • opnsense core <= 26.1.10; <= 26.4.1
no check availablenot proven exploitable
3d 14h 17msince last run(AI 16m)Analysis: how long the AI spent reversing this signal.
cvss8.0cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−106dkevAttacks confirmed in the real world.
CVE-2026-100349ETK-2026-1694Zero'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 • getkin kin-openapi <= 0.145.0
no check availablenot proven exploitable
5d 15h 06msince last run(AI 16m)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).−73dkevAttacks confirmed in the real world.
CVE-2026-59774ETK-2026-1692Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
15 Oct 2026 • Gitea 1.22 < 1.27.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.
+1.1dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI <1m)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.1dkevAttacks confirmed in the real world.+1d
CVE-2026-110958ETK-2026-1691Zero'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 • Wavlink WN530HG4B M30HG4B_V260724
no check availablenot proven exploitable
5d 14h 17msince last run(AI 21m)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).+1h01mkevAttacks confirmed in the real world.
CVE-2026-57155ETK-2026-1690Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
15 Oct 2026 • opnsense core <= 26.1.10; <= 26.4.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.
+2h05mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 53m)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).−91dkevAttacks confirmed in the real world.
CVE-2026-102469ETK-2026-1658Zero'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 • Eclipse Foundation Eclipse Vert.x 5.2.0; >=5.0.0, <=5.1.8; <=4.5.34
no check availablenot proven exploitable
5d 22h 32msince last run(AI 29m)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).−7.4dkevAttacks confirmed in the real world.
CVE-2026-55683ETK-2026-1649Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
14 Oct 2026 • LabRedesCefetRJ WeGIA <=3.8.5
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+10h47mTTVTime-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.8cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−121dkevAttacks confirmed in the real world.
CVE-2026-55680ETK-2026-1648Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
14 Oct 2026 • LabRedesCefetRJ WeGIA <= 3.8.5
check availableZero validated a working check for it.proven exploitableZero has validated a full working exploit.
+10h45mTTVTime-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.
cvss9.8cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−121dkevAttacks confirmed in the real world.
CVE-2026-55684ETK-2026-1647Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
14 Oct 2026 • LabRedesCefetRJ WeGIA <= 3.8.5
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+10h14mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 14m)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).−121dkevAttacks confirmed in the real world.
CVE-2026-57490ETK-2026-1639Zero'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 • error311 FileRise ≤ 3.15.0
no check availablenot proven exploitable
6d 03h 21msince last run(AI 14m)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).−112dkevAttacks confirmed in the real world.
CVE-2026-0322ETK-2026-1636Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
14 Oct 2026 • Palo Alto Networks PAN-OS >= 12.2.0, < 12.2.4; >= 12.1.0, < 12.1.10-h2; >= 11.2.0, < 11.2.16; >= 11.1.0, < 11.1.16-h3; >= 10.2.0, < 10.2.18-h12
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+10h31mTTVTime-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.6cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+9h50mkevAttacks confirmed in the real world.+2h01m
CVE-2026-0993ETK-2026-1631Zero'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 • SODOLA SL902-SWTGW124AS <= 200.2.12
no check availablenot proven exploitable
6d 04h 15msince last run(AI 34m)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-71854ETK-2026-1623Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
14 Oct 2026 • OpenAEV-Platform openaev 2.260604.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.4dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 1h 02m)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).−26dkevAttacks confirmed in the real world.
ETK-2026-1622Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
14 Oct 2026 • go:github.com/stacklok/toolhive >= 0.9.1, < 0.52.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.
−6.2dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.and counting(AI 27m)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).−6.6dkevAttacks confirmed in the real world.
CVE-2026-110858ETK-2026-1615Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
30 Sep 2026 • gitpython-developers GitPython >= 3.1.30, < 3.2.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.
−13dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 11m)Analysis: how long the AI spent reversing this signal.
cvss9.2cve.org+13dpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−15dkevAttacks confirmed in the real world.
CVE-2026-110536ETK-2026-1609Zero'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 • D-Link DIR-868L 2.01b05
no check availablenot proven exploitable
6d 08h 38msince last run(AI 53m)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).−16dkevAttacks confirmed in the real world.
CVE-2026-96889ETK-2026-1604Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
23 Sep 2026 • npm:next >= 10.0.0 <= 15.5.27; > 16.0.0 <= 16.4.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.
+21dTTVTime-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.
cvss9.5cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−2.0dkevAttacks confirmed in the real world.
CVE-2026-102748ETK-2026-1600Zero'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 • dgraph-io dgraph <=25.3.8
no check availablenot proven exploitable
6d 12h 16msince last run(AI 14m)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).−73dkevAttacks confirmed in the real world.
CVE-2026-76519ETK-2026-1595Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
14 Oct 2026 • Cisco Secure Email 14.0.0-698; 13.5.1-277; 13.0.0-392; 14.2.0-620; 13.0.5-007; 13.5.4-038; 14.2.1-020; 14.3.0-032; 15.0.0-104; 15.0.1-030; 15.5.0-048; 15.5.1-055; 15.5.2-018; 16.0.0-050; 15.0.3-002; 16.0.0-054; 15.5.3-022; 16.0.1-017; 15.5.4-012; 16.0.4-016; 15.0.5-016; 16.0.2-112; 16.0.3-044
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+2h25mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 14m)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).+3h59mkevAttacks confirmed in the real world.+3h20m