validatingCVE-2026-5638811m
CVE-2026-89425waiting for further signals+16mCVE-2026-47360waiting for further signals+20mCVE-2026-100636check available+26mCVE-2026-100637check available+14mCVE-2023-54404check available+14mCVE-2026-100638waiting for further signals+21mCVE-2026-100646check available+35mCVE-2026-102989check available+22mCVE-2026-92574waiting for further signals+18mCVE-2026-12405waiting for further signals+1h 38m

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,2687% before t=0
1,500 of 2,268 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 2,263 entries
listcard
CVE-2026-89425ETK-2026-268Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
23 Sep 2026 • maven:com.fasterxml.jackson.core:jackson-core >= 2.19.0, <= 2.21.6; >= 2.22.0, <= 2.22.2; >= 3.0.0, <= 3.1.6; >= 3.2.0, <= 3.2.2; >= 2.8.0, <= 2.18.10
no check availablenot proven exploitable
19d 17h 47msince last run(AI 16m)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).+8.6dkevAttacks confirmed in the real world.
CVE-2026-47360ETK-2026-267Zero'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 • Apache Software Foundation Apache HTTP Server >= 2.4.0, <= 2.4.68
no check availablenot proven exploitable
19d 16h 14msince last run(AI 20m)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-100636ETK-2026-266Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
26 Sep 2026 • go:github.com/siyuan-note/siyuan <= 3.8.3
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+7.2dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 26m)Analysis: how long the AI spent reversing this signal.
cvss7.6cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−16dkevAttacks confirmed in the real world.
CVE-2026-100637ETK-2026-265Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
26 Sep 2026 • go:github.com/siyuan-note/siyuan <= 3.8.3
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+5.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.
cvss7.6cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−16dkevAttacks confirmed in the real world.
CVE-2023-54404ETK-2026-264Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
1 Oct 2026 • colinhacks zod <= 4.6.5
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+1h00mTTVTime-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.
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.
CVE-2026-100638ETK-2026-263Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
26 Sep 2026 • go:github.com/siyuan-note/siyuan <= 3.8.3
no check availablenot proven exploitable
19d 18h 09msince last run(AI 21m)Analysis: how long the AI spent reversing this signal.
cvss7.6cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−16dkevAttacks confirmed in the real world.
CVE-2026-100646ETK-2026-262Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
26 Sep 2026 • go:github.com/siyuan-note/siyuan <= 3.8.3
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+5.2dTTVTime-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.
cvss9.3cve.orgpublic 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-102989ETK-2026-261Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
30 Sep 2026 • npm:@tanstack/start-server-core >= 1.143.12, < 1.169.39; >= 1.143.12, < 1.168.60; >= 1.143.12, < 1.168.57; >= 1.143.12, < 1.168.56
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
−12dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 22m)Analysis: how long the AI spent reversing this signal.
cvss9.3cve.org+12dpublic 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-92574ETK-2026-260Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
21 Sep 2026 • CRI-O <=1.36.5; <=1.35.8; <=1.34.13
no check availablenot proven exploitable
19d 18h 52msince last run(AI 18m)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-12405ETK-2026-259Zero'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 • Red Hat Satellite 6.19 for RHEL 9
no check availablenot proven exploitable
19d 13h 04msince last run(AI 1h 38m)Analysis: how long the AI spent reversing this signal.
cvss8.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-96659ETK-2026-258Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
1 Oct 2026 • Red Hat Satellite 6.19 for RHEL 9
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+4h16mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 1h 27m)Analysis: how long the AI spent reversing this signal.
cvss9.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-96658ETK-2026-257Zero'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 • Red Hat Satellite 6.19 for RHEL 9
no check availablenot proven exploitable
19d 16h 14msince last run(AI 1h 28m)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-79898ETK-2026-256Zero'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 • Fortra BoKS Manager >= 8.1.0.0, <= 8.1.0.23; >= 9.0.0.0, <= 9.0.0.6
no check availablenot proven exploitable
19d 19h 20msince last run(AI 24m)Analysis: how long the AI spent reversing this signal.
cvss9.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-92951ETK-2026-255Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
17 Sep 2026 • npm:vm2 <= 3.11.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.
+14dTTVTime-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.
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-92957ETK-2026-254Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
17 Sep 2026 • npm:vm2 <= 3.11.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.
+14dTTVTime-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.
cvss9.9cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+14dkevAttacks confirmed in the real world.
CVE-2026-92937ETK-2026-253Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
17 Sep 2026 • npm:vm2 = 3.11.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.
+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.
cvss10.0cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+14dkevAttacks confirmed in the real world.
CVE-2026-92940ETK-2026-252Zero'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.3, <= 3.11.6
no check availablenot proven exploitable
19d 19h 58msince last run(AI 13m)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).+14dkevAttacks confirmed in the real world.
CVE-2026-92941ETK-2026-251Zero'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.3, <= 3.11.6
no check availablenot proven exploitable
19d 19h 57msince last run(AI 15m)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).kevAttacks confirmed in the real world.
CVE-2026-62071ETK-2026-250Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
1 Oct 2026 • nickboss WordPress File Upload >= n/a, <= 5.1.10
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+1h53mTTVTime-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.
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-103752ETK-2026-249Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
1 Oct 2026 • Paul Ryan Authorizer >= n/a, <= 3.15.3
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+2h57mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 1h 44m)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).+13h44mkevAttacks confirmed in the real world.