validatingCVE-2026-1029997m
CVE-2026-113711waiting for further signals+25mCVE-2026-96451check available+37mCVE-2026-104991waiting for further signals+26mETK-2026-463check available+17mCVE-2026-105113waiting for further signals+22mCVE-2026-93591waiting for further signals+16mCVE-2026-92084check available+43mCVE-2026-104637waiting for further signals+18mETK-2026-405check available+22mCVE-2026-63209waiting for further signals+11m

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% validated988 of 2,2327% before t=0
1,500 of 2,232 drawn
CVE-2026-103068
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 21m
How fast Zero starts validating it
step 3
validated
+5h 07m
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 449 entries
listcard
CVE-2026-113711ETK-2026-481Zero'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:apostrophe < 4.33.0; < 3.7.0
no check availablenot proven exploitable
9h 11msince 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).−18dkevAttacks confirmed in the real world.cvss7.5
CVE-2026-96451ETK-2026-473Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
3 Oct 2026 • Ultimate Member <= 2.13.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.
+1h47mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 37m)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).+21h43mkevAttacks confirmed in the real world.cvss8.8
CVE-2026-104991ETK-2026-471Zero'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 • Alanaktion phproject <= 1.8.6
no check availablenot proven exploitable
16d 09h 14msince last run(AI 26m)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.7dkevAttacks confirmed in the real world.cvss7.1
ETK-2026-463Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
30 Sep 2026 • pip GitPython <= 3.1.62
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
−18dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.and counting(AI 17m)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).−21dkevAttacks confirmed in the real world.cvss7.0
CVE-2026-105113ETK-2026-460Zero'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 • nezhahq nezha >= 1.8.0, < 2.3.13
no check availablenot proven exploitable
17d 13h 38msince last run(AI 22m)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.cvss7.1
CVE-2026-93591ETK-2026-458Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
18 Sep 2026 • go:github.com/siyuan-note/siyuan/kernel <= 3.8.2
no check availablenot proven exploitable
17d 14h 14msince last run(AI 16m)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.cvss7.6
CVE-2026-92084ETK-2026-435Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
3 Oct 2026 • beaverbuilder Beaver Builder Page Builder – Drag and Drop Website Builder <= 2.11.0.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.
+1h27mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 43m)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.1dkevAttacks confirmed in the real world.cvss9.1
CVE-2026-104637ETK-2026-412Zero'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 • onetwothreeneth HospitalManagementSystem
no check availablenot proven exploitable
17d 23h 35msince last run(AI 18m)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).+0mkevAttacks confirmed in the real world.cvss7.3
ETK-2026-405Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
2 Oct 2026 • npm:trigger.dev <= 4.5.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.
−17dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.and counting(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).−18dkevAttacks confirmed in the real world.cvss7.1
CVE-2026-63209ETK-2026-401Zero'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 • klauspost:compress/s2 <= v1.18.6
no check availablenot proven exploitable
18d 01h 48msince last run(AI 11m)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).−91dkevAttacks confirmed in the real world.cvss7.5
CVE-2026-68496ETK-2026-400Zero'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 • fasterxml jackson-dataformats-binary >= 2.16.0, <= 2.18.9; >= 2.19.0, <= 2.21.5; >= 2.22.0, <= 2.22.1; >= 3.0.0, <= 3.1.5; >= 3.2.0, <= 3.2.1
no check availablenot proven exploitable
18d 01h 51msince last run(AI 10m)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).+39mkevAttacks confirmed in the real world.cvss7.5
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 16h 29msince 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).+3.4dkevAttacks confirmed in the real world.cvss9.4
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 02h 32msince last run(AI 29m)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).−18dkevAttacks confirmed in the real world.cvss7.7
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 02h 54msince 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).−48dkevAttacks confirmed in the real world.cvss7.5
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 03h 49msince last run(AI 28m)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).−18dkevAttacks confirmed in the real world.cvss8.2