validatingCVE-2026-870958m
CVE-2026-105080waiting for further signals+8mCVE-2026-103957waiting for further signals+18mETK-2026-393waiting for further signals+29mCVE-2026-104861waiting for further signals+12mCVE-2026-103958waiting for further signals+14mCVE-2026-104433waiting for further signals+21mETK-2026-389waiting for further signals+28mETK-2026-385waiting for further signals+44mETK-2026-384waiting for further signals+25mETK-2026-383waiting for further signals+20m

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).
20 of 1,243 entries
listcard
CVE-2026-105080ETK-2026-395Zero'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 • C4illin ConvertX < 0.19.0
no check availablenot proven exploitable
14d 23h 14msince last run(AI 8m)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).+3.4dkevAttacks confirmed in the real world.
CVE-2026-103957ETK-2026-394Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
2 Oct 2026 • AWS loom <1.7.0
no check availablenot proven exploitable
18d 09h 23msince 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-393Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
2 Oct 2026 • npm:trigger.dev <= 4.5.5
no check availablenot proven exploitable
18d 09h 17msince last run(AI 29m)Analysis: how long the AI spent reversing this signal.
cvss7.7awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−19dkevAttacks confirmed in the real world.
CVE-2026-104861ETK-2026-392Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
2 Oct 2026 • nodeca probe-image-size <=7.3.0
no check availablenot proven exploitable
18d 09h 39msince last run(AI 12m)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).−48dkevAttacks confirmed in the real world.
CVE-2026-103958ETK-2026-391Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
2 Oct 2026 • AWS loom <1.7.0
no check availablenot proven exploitable
17d 09h 56msince last run(AI 14m)Analysis: how long the AI spent reversing this signal.
cvss8.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-104433ETK-2026-390Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
2 Oct 2026 • kvcache-ai Mooncake < 0.3.12
no check availablenot proven exploitable
18d 08h 15msince last run(AI 21m)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.
ETK-2026-389Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
2 Oct 2026 • go:github.com/siyuan-note/siyuan/kernel < 0.0.0-20260813142806-dd2778b70d02
no check availablenot proven exploitable
18d 10h 34msince last run(AI 28m)Analysis: how long the AI spent reversing this signal.
cvss8.2awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−18dkevAttacks confirmed in the real world.
ETK-2026-385Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
2 Oct 2026 • npm:trigger.dev < 4.5.2
no check availablenot proven exploitable
17d 10h 10msince last run(AI 44m)Analysis: how long the AI spent reversing this signal.
cvss7.1awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−19dkevAttacks confirmed in the real world.
ETK-2026-384Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
2 Oct 2026 • npm:trigger.dev <= 4.5.5
no check availablenot proven exploitable
18d 11h 16msince last run(AI 25m)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).−19dkevAttacks confirmed in the real world.
ETK-2026-383Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
2 Oct 2026 • npm:trigger.dev < 4.5.4
no check availablenot proven exploitable
18d 11h 28msince last run(AI 20m)Analysis: how long the AI spent reversing this signal.
cvss9.2awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−19dkevAttacks confirmed in the real world.
CVE-2026-82041ETK-2026-379Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
2 Oct 2026 • UTMStack < 11.2.16
no check availablenot proven exploitable
18d 11h 42msince last run(AI 1h 23m)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).kevAttacks confirmed in the real world.
CVE-2026-104019ETK-2026-378Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
2 Oct 2026 • AWS sagemaker-distribution 2.14.x: < 2.14.12; 3.9.x: < 3.9.12; 4.0.x: < 4.0.11; 4.1.x: < 4.1.11; 4.2.x: < 4.2.8; 4.3.x: < 4.3.5; 4.4.x: < 4.4.3; 2.8.x - 2.13.x
no check availablenot proven exploitable
18d 12h 56msince last run(AI 18m)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).kevAttacks confirmed in the real world.
CVE-2026-111767ETK-2026-376Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
2 Oct 2026 • npm:@modelcontextprotocol/sdk >= 1.24.0, < 1.32.0
no check availablenot proven exploitable
16h 12msince last run(AI 13m)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-82042ETK-2026-374Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
2 Oct 2026 • UTMStack < 11.2.16
no check availablenot proven exploitable
18d 09h 40msince last run(AI 53m)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).kevAttacks confirmed in the real world.
CVE-2026-104988ETK-2026-372Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
2 Oct 2026 • Red Hat Certificate System 10
no check availablenot proven exploitable
14d 07h 57msince last run(AI 1h 09m)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).kevAttacks confirmed in the real world.
CVE-2023-54405ETK-2026-367Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
2 Oct 2026 • H3C CVM *
no check availablenot proven exploitable
16d 11h 35msince last run(AI 24m)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).kevAttacks confirmed in the real world.0d
CVE-2026-104908ETK-2026-363Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
2 Oct 2026 • MISP < 2.5.48
no check availablenot proven exploitable
18d 10h 44msince last run(AI 32m)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).kevAttacks confirmed in the real world.
CVE-2026-104912ETK-2026-361Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
2 Oct 2026 • MISP < 2.5.48
no check availablenot proven exploitable
10d 05h 39msince last run(AI 34m)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).kevAttacks confirmed in the real world.
CVE-2026-66859ETK-2026-360Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
2 Oct 2026 • Apache Software Foundation Apache Thrift < 0.25.0
no check availablenot proven exploitable
18d 17h 10msince last run(AI 23m)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.
CVE-2026-66858ETK-2026-359Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
2 Oct 2026 • Apache Software Foundation Apache Thrift < 0.25.0
no check availablenot proven exploitable
18d 17h 19msince last run(AI 16m)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.