validatingCVE-2026-9299813m
ETK-2026-706waiting for further signals+22mETK-2026-705waiting for further signals+20mCVE-2026-91107waiting for further signals+8mCVE-2026-21589check available+35mETK-2026-702waiting for further signals+37mCVE-2026-104976waiting for further signals+23mCVE-2026-104979waiting for further signals+1h 02mCVE-2026-105630waiting for further signals+52mCVE-2026-102826check available+14mCVE-2026-102827waiting for further signals+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. The curve shows how many were confirmed at each point in time; a dot is one still validating or waiting for its CVE. The further left, the earlier it was confirmed. The centre line is the moment the vulnerability was fully disclosed on cve.org.
timelinedistribution
44% validated998 of 2,2557% before t=0
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 21m
How fast Zero starts validating it
step 3
validated
+4h 53m
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).
15 of 2,250 entries
listcard
ETK-2026-706Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
5 Oct 2026 • unci >= 1.22.0, <= 1.23.5
no check availablenot proven exploitable
15d 07h 38msince last run(AI 22m)Analysis: how long the AI spent reversing this signal.
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.cvss7.5
ETK-2026-705Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
5 Oct 2026 • libheif >= 1.17.0, <= 1.23.5
no check availablenot proven exploitable
15d 07h 40msince last run(AI 20m)Analysis: how long the AI spent reversing this signal.
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−16dkevAttacks confirmed in the real world.cvss7.5
CVE-2026-91107ETK-2026-704Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
5 Oct 2026 • os4ed openSIS-Classic 9.3
no check availablenot proven exploitable
15d 08h 00msince last run(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).kevAttacks confirmed in the real world.cvss9.3
CVE-2026-21589ETK-2026-703Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
5 Oct 2026 • atlassian Bamboo Data Center All other versions; All versions
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+21h16mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 35m)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).+13h11mkevAttacks confirmed in the real world.+2dcvss9.3
ETK-2026-702Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
5 Oct 2026 • libheif >= 1.19.0, <= 1.23.5
no check availablenot proven exploitable
15d 07h 49msince last run(AI 37m)Analysis: how long the AI spent reversing this signal.
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−16dkevAttacks confirmed in the real world.cvss7.5
CVE-2026-104976ETK-2026-701Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
5 Oct 2026 • makeplane plane <= 1.3.1
no check availablenot proven exploitable
15d 08h 26msince 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).kevAttacks confirmed in the real world.cvss8.7
CVE-2026-104979ETK-2026-700Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
5 Oct 2026 • makeplane plane <= 1.3.1
no check availablenot proven exploitable
14d 06h 09msince last run(AI 1h 02m)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).−7.4dkevAttacks confirmed in the real world.cvss8.7
CVE-2026-105630ETK-2026-699Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
5 Oct 2026 • makeplane plane <= 1.3.1
no check availablenot proven exploitable
15d 08h 08msince last run(AI 52m)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).−7.5dkevAttacks confirmed in the real world.cvss8.7
CVE-2026-102826ETK-2026-698Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
29 Sep 2026 • npm:simple-git <= 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.
+6.2dTTVTime-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.
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.1
CVE-2026-102827ETK-2026-697Zero'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 • npm:simple-git <= 3.36.0
no check availablenot proven exploitable
6d 17h 55msince last run(AI 14m)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).+14dkevAttacks confirmed in the real world.cvss8.1
CVE-2026-100721ETK-2026-696Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
27 Sep 2026 • npm:vm2 <= 3.12.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.
+9.0dTTVTime-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.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+1.3dkevAttacks confirmed in the real world.cvss10.0
CVE-2026-105764ETK-2026-695Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
5 Oct 2026 • immich-app immich v3.2.2
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+1h02mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(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.cvss7.7
CVE-2026-105762ETK-2026-694Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
5 Oct 2026 • langgenius dify < 1.13.0
no check availablenot proven exploitable
15d 09h 19msince last run(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).−140dkevAttacks confirmed in the real world.cvss8.3
CVE-2026-105763ETK-2026-693Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
5 Oct 2026 • twentyhq twenty >= 1.20.10, < 2.7.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.
+1h14mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 39m)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.6
CVE-2026-92947ETK-2026-692Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
17 Sep 2026 • npm:vm2 <= 3.11.6
no check availablenot proven exploitable
15d 09h 43msince 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).+18dkevAttacks confirmed in the real world.cvss10.0