validatingCVE-2026-1144052m
CVE-2026-97679check available+46mCVE-2026-97678check available+36mCVE-2026-105677waiting for further signals+2h 55mCVE-2026-105643check available+32mCVE-2026-43598waiting for further signals+13mCVE-2026-61411check available+33mCVE-2026-105862check available+41mCVE-2026-83540waiting for further signals+8mCVE-2026-106471check available+46mCVE-2026-14911waiting for further signals+12m

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% validated1,010 of 2,2837% 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 17m
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).
15 of 2,283 entries
listcard
CVE-2026-97679ETK-2026-845Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
6 Oct 2026 • IBM Langflow OSS >= 1.0.0, <= 1.12.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.
+5h28mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 46m)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.8
CVE-2026-97678ETK-2026-844Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
6 Oct 2026 • IBM Langflow OSS >= 1.0.0, <= 1.12.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.
+5h11mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 36m)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.8
CVE-2026-105677ETK-2026-843Zero'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 • npm Ghost >= 6.10.3, < 6.64.0
no check availablenot proven exploitable
14d 09h 25msince last run(AI 2h 55m)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.2
CVE-2026-105643ETK-2026-842Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
5 Oct 2026 • npm Ghost >= 6.34.0, < 6.67.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.
+2.3dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 32m)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.3
CVE-2026-43598ETK-2026-841Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
6 Oct 2026 • AMD Instinct™ MI210
no check availablenot proven exploitable
14d 12h 20msince last run(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).kevAttacks confirmed in the real world.cvss7.7
CVE-2026-61411ETK-2026-840Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
6 Oct 2026 • dell Container Storage Modules >= 0, < 1.18.0 or later
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+12h54mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 33m)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-105862ETK-2026-839Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
6 Oct 2026 • payloadcms payload < 3.90.0; >= 4.0.0-canary.0, < 4.0.0-canary.34
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 41m)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-83540ETK-2026-838Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
7 Oct 2026 • wolfSSL wolfSSH >= 1.4.15, <= 1.5.0
no check availablenot proven exploitable
14d 08h 50msince 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.cvss7.7
CVE-2026-106471ETK-2026-837Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
7 Oct 2026 • Red Hat Satellite 6
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+1h41mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 46m)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-14911ETK-2026-836Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
7 Oct 2026 • ASUS Router 3.0.0.6.102 series
no check availablenot proven exploitable
10d 06h 45msince last run(AI 12m)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-106492ETK-2026-835Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
6 Oct 2026 • backstage < 0.17.8
no check availablenot proven exploitable
13d 12h 06msince last run(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).kevAttacks confirmed in the real world.cvss7.6
CVE-2026-102478ETK-2026-834Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
7 Oct 2026 • Octopus Deploy Octopus Server >= 2023.2.945, < 2026.1.11768; >= 2026.2.0, < 2026.2.13408; >= 2026.3.0, < 2026.3.15816
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+1h43mTTVTime-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.
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-105324ETK-2026-833Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
7 Oct 2026 • ASUSTOR Inc. ADM >= 5.0.0, <= 5.1.4.RL21; >= 4.1.0, <= 4.3.3.RWC1
no check availablenot proven exploitable
14d 14h 08msince last run(AI 25m)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-97673ETK-2026-832Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
7 Oct 2026 • IBM Langflow OSS >= 1.0.0, <= 1.12.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.
+1h50mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(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.8
CVE-2026-93675ETK-2026-831Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
7 Oct 2026 • IBM Langflow OSS >= 1.0.0, <= 1.12.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.
+6h28mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 32m)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.8