validatingCVE-2026-8709517m
CVE-2026-84782waiting for further signals+18mETK-2026-544waiting for further signals+36mCVE-2026-105135waiting for further signals+36mCVE-2026-84783waiting for further signals+24mCVE-2026-51878waiting for further signals+32mCVE-2026-81809waiting for further signals+28mCVE-2026-87970waiting for further signals+51mCVE-2026-87973waiting for further signals+37mCVE-2026-89296waiting for further signals+36mCVE-2026-96200waiting for further signals+33m

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,2727% before t=0
1,500 of 2,272 drawn
CVE-2026-70197
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 19m
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 1,249 entries
listcard
CVE-2026-84782ETK-2026-545Zero'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 • OpenSSL >= 4.0.0, < 4.0.3; >= 3.6.0, < 3.6.5; >= 3.5.0, < 3.5.9; >= 3.4.0, < 3.4.8; >= 3.0.0, < 3.0.23; >= 1.1.1, < 1.1.1zj; >= 1.0.2, < 1.0.2zs
no check availablenot proven exploitable
17d 04h 33msince last run(AI 18m)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).kevAttacks confirmed in the real world.
ETK-2026-544Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
4 Oct 2026 • other:AiSOC (services/api) <= 16.0.0
no check availablenot proven exploitable
17d 04h 36msince last run(AI 36m)Analysis: how long the AI spent reversing this signal.
cvss7.0awaiting cvepublic 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-105135ETK-2026-542Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
4 Oct 2026 • InternLM MindSearch 0.1.0
no check availablenot proven exploitable
13d 01h 43msince last run(AI 36m)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).+0mkevAttacks confirmed in the real world.
CVE-2026-84783ETK-2026-541Zero'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 • OpenSSL >= 4.0.0, < 4.0.3
no check availablenot proven exploitable
17d 04h 29msince 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).kevAttacks confirmed in the real world.
CVE-2026-51878ETK-2026-539Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
1 Oct 2026 • deeptutor n/a
no check availablenot proven exploitable
17d 06h 31msince last run(AI 32m)Analysis: how long the AI spent reversing this signal.
cvss4.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-81809ETK-2026-536Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
1 Oct 2026 • Paytm Payment Gateway < 2.8.9
no check availablenot proven exploitable
17d 04h 25msince last run(AI 28m)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-87970ETK-2026-533Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
1 Oct 2026 • If-So Dynamic Content >= 1.8, < 1.10.2
no check availablenot proven exploitable
17d 07h 05msince last run(AI 51m)Analysis: how long the AI spent reversing this signal.
cvss4.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-87973ETK-2026-532Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
1 Oct 2026 • If-So Dynamic Content >= 1.9.9, < 1.10.2
no check availablenot proven exploitable
16d 07h 06msince last run(AI 37m)Analysis: how long the AI spent reversing this signal.
cvss3.1cve.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-89296ETK-2026-531Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
1 Oct 2026 • Pro Like Button < 2.0
no check availablenot proven exploitable
17d 07h 40msince last run(AI 36m)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).kevAttacks confirmed in the real world.
CVE-2026-96200ETK-2026-526Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
1 Oct 2026 • Payments for Hubtel < 1.0.2
no check availablenot proven exploitable
17d 09h 10msince last run(AI 33m)Analysis: how long the AI spent reversing this signal.
cvss5.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-88779ETK-2026-525Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
4 Oct 2026 • NetScaler ADC < 14.1-73.41; < 13.1-64.28; < 13.1-37.282; >= 0, < 14.1-73.41 FIPS
no check availablenot proven exploitable
15d 01h 36msince last run(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).kevAttacks confirmed in the real world.−2d
CVE-2026-96255ETK-2026-524Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
1 Oct 2026 • Payments for Hubtel < 1.0.2
no check availablenot proven exploitable
17d 10h 04msince last run(AI 32m)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-84446ETK-2026-523Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
18 Sep 2026 • strukturag libheif <= 1.23.1
no check availablenot proven exploitable
17d 10h 26msince last run(AI 1h 18m)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-84384ETK-2026-522Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
18 Sep 2026 • strukturag libheif <= 1.23.1
no check availablenot proven exploitable
17d 11h 44msince 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).kevAttacks confirmed in the real world.
CVE-2026-84447ETK-2026-521Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
18 Sep 2026 • strukturag libheif <= 1.23.1
no check availablenot proven exploitable
17d 11h 39msince 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).kevAttacks confirmed in the real world.
CVE-2026-105129ETK-2026-518Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
3 Oct 2026 • laradashboard v1.4.2
no check availablenot proven exploitable
17d 12h 03msince last run(AI 30m)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).−14h01mkevAttacks confirmed in the real world.
CVE-2026-85532ETK-2026-514Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
30 Sep 2026 • Apache Software Foundation Apache WSS4J >= 4.0.0, < 4.0.2; >= 3.0.0, < 3.0.6; < 2.4.4
no check availablenot proven exploitable
17d 13h 21msince last run(AI 14m)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-88920ETK-2026-511Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
30 Sep 2026 • Apache Software Foundation Apache WSS4J >= 4.0.0, < 4.0.2; >= 3.0.0, < 3.0.6; < 2.4.4
no check availablenot proven exploitable
17d 13h 58msince last run(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).kevAttacks confirmed in the real world.
CVE-2026-96886ETK-2026-510Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
30 Sep 2026 • Course Booking System >= 7.0, < 7.0.9
no check availablenot proven exploitable
17d 12h 55msince last run(AI 1h 31m)Analysis: how long the AI spent reversing this signal.
cvss5.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-5430ETK-2026-506Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
15 Sep 2026 • WSO2 Universal Gateway >= 4.5.0, < 4.5.0.57; >= 4.6.0, < 4.6.0.21; >= 4.5.0, < 4.5.0.56; >= 4.5.0, < 4.5.0.58; >= 4.6.0, < 4.6.0.22; >= 4.1.0, < 4.1.0.257; >= 4.2.0, < 4.2.0.197; >= 4.3.0, < 4.3.0.108; >= 4.4.0, < 4.4.0.72; >= 9.20.74, < 9.20.74.401; >= 9.28.116, < 9.28.116.417; >= 9.29.120, < 9.29.120.236; >= 9.30.67, < 9.30.67.167; >= 9.31.86, < 9.31.86.158; >= 9.32.147, < 9.32.147.59
no check availablenot proven exploitable
17d 08h 30msince last run(AI 30m)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).+51dkevAttacks confirmed in the real world.+40d