validatingCVE-2026-8709510m
CVE-2026-65660check available+29mCVE-2026-67279kev listed+23mCVE-2026-88771check available+8mCVE-2026-88772kev listed+15mCVE-2026-102828check available+19mCVE-2026-102829check available+13mCVE-2026-102559waiting for further signals+20mCVE-2026-102556waiting for further signals+38mCVE-2026-102268check available+17m

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,003 of 2,2637% before t=0
1,500 of 2,263 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).
9 of 2,064 entries
listcard
CVE-2026-65660ETK-2026-9Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
25 Sep 2026 • Microsoft SharePoint >= 16.0.0, < 16.0.5565.1001; >= 16.0.0, < 16.0.10417.20198; >= 16.0.0, < 16.0.19725.20522
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+51dTTVTime-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.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+45dkevAttacks confirmed in the real world.+44dcvss8.8
CVE-2026-67279ETK-2026-8Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
25 Sep 2026 • MikroTik RouterOS >= 7.24, < 7.24.2; >= 7.0.0, < 7.23.4; >= 6.0.0, < 6.49.21
no check availablenot proven exploitable
19d 09h 56msince last run(AI 23m)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).+20dkevAttacks confirmed in the real world.0dcvss6.5
CVE-2026-88771ETK-2026-7Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
27 Sep 2026 • Citrix NetScaler < 14.1-73.37; < 13.1-64.23; >= 0, < 14.1-73.37 FIPS; >= 0, < 13.1.37.279 FIPS and NDcPP
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+4.4dTTVTime-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.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+2h14mkevAttacks confirmed in the real world.+5h28mcvss9.8
CVE-2026-88772ETK-2026-6Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
27 Sep 2026 • Citrix NetScaler < 14.1-73.37; < 13.1-64.23; >= 0, < 14.1-73.37 FIPS; >= 0, < 13.1.37.279 FIPS and NDcPP
no check availablenot proven exploitable
19d 09h 26msince 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).+2h06mkevAttacks confirmed in the real world.+5h21mcvss8.1
CVE-2026-102828ETK-2026-5Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
29 Sep 2026 • steveukx git-js = 3.15.0; <= 3.36.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.
+1h35mTTVTime-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).kevAttacks confirmed in the real world.cvss9.2
CVE-2026-102829ETK-2026-4Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
29 Sep 2026 • steveukx git-js < 2.0.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.
+14dTTVTime-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).−3.2dkevAttacks confirmed in the real world.cvss9.2
CVE-2026-102559ETK-2026-3Zero'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 • Red Hat Enterprise Linux 10
no check availablenot proven exploitable
7d 11h 21msince last run(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).kevAttacks confirmed in the real world.cvss8.6
CVE-2026-102556ETK-2026-2Zero'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 • Red Hat Enterprise Linux 10
no check availablenot proven exploitable
7d 04h 57msince last run(AI 38m)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).kevAttacks confirmed in the real world.cvss8.6
CVE-2026-102268ETK-2026-1Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
28 Sep 2026 • pip:PyJWT <= 2.13.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.
+23h36mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 17m)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).+3.7dkevAttacks confirmed in the real world.cvss9.1