validatingCVE-2026-870959m
ETK-2026-1359waiting for further signals+10mETK-2026-1344waiting for further signals+16mCVE-2026-108807waiting for further signals+23mCVE-2025-70518waiting for further signals+39mETK-2026-1323waiting for further signals+13mCVE-2026-108783waiting for further signals+9mETK-2026-1292waiting for further signals+14mETK-2026-1291waiting for further signals+14mETK-2026-1288waiting for further signals+13mCVE-2026-108980waiting for further signals+8m

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,003 of 2,2637% 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 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 453 entries
listcard
ETK-2026-1359Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
12 Oct 2026 • npm:dompurify >= 3.4.4, <= 3.4.16
no check availablenot proven exploitable
8d 21h 41msince last run(AI 10m)Analysis: how long the AI spent reversing this signal.
cvss7.2awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−8.9dkevAttacks confirmed in the real world.
ETK-2026-1344Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
12 Oct 2026 • go:klauspost/compress/zstd <= v1.20.1
no check availablenot proven exploitable
8d 23h 24msince last run(AI 16m)Analysis: how long the AI spent reversing this signal.
cvss7.0awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−9.0dkevAttacks confirmed in the real world.
CVE-2026-108807ETK-2026-1342Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
12 Oct 2026 • krupalshah EmployeeRecruitmentSystem
no check availablenot proven exploitable
9d 00h 23msince last run(AI 23m)Analysis: how long the AI spent reversing this signal.
cvss7.3cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+0mkevAttacks confirmed in the real world.
CVE-2025-70518ETK-2026-1332Zero'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 • Fanvil x7a n/a
no check availablenot proven exploitable
9d 01h 43msince last run(AI 39m)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).+16h05mkevAttacks confirmed in the real world.
ETK-2026-1323Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
12 Oct 2026 • npm:i18next >= 25.3.3, < 26.4.4
no check availablenot proven exploitable
9d 02h 53msince last run(AI 13m)Analysis: how long the AI spent reversing this signal.
cvss7.5awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−9.2dkevAttacks confirmed in the real world.
CVE-2026-108783ETK-2026-1293Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
12 Oct 2026 • prvtpro Amnezia-Web-Panel 1.6.0; 1.6.1; 1.6.2; 1.7.0; 1.7.1; 1.7.2
no check availablenot proven exploitable
9d 06h 51msince last run(AI 9m)Analysis: how long the AI spent reversing this signal.
cvss7.3cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+0mkevAttacks confirmed in the real world.
ETK-2026-1292Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
9 Oct 2026 • pip:turbohtml >= 1.1.0, <= 1.13.1
no check availablenot proven exploitable
9d 06h 50msince last run(AI 14m)Analysis: how long the AI spent reversing this signal.
cvss7.5awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−12dkevAttacks confirmed in the real world.
ETK-2026-1291Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
9 Oct 2026 • pip:turbohtml >= 1.0.0, <= 1.13.1
no check availablenot proven exploitable
9d 06h 58msince last run(AI 14m)Analysis: how long the AI spent reversing this signal.
cvss7.5awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−12dkevAttacks confirmed in the real world.
ETK-2026-1288Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
9 Oct 2026 • pip:turbohtml >= 1.1.0, <= 1.13.1
no check availablenot proven exploitable
9d 07h 16msince last run(AI 13m)Analysis: how long the AI spent reversing this signal.
cvss7.5awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−12dkevAttacks confirmed in the real world.
CVE-2026-108980ETK-2026-1281Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
12 Oct 2026 • Blinko <= 1.8.8
no check availablenot proven exploitable
9d 06h 52msince last run(AI 8m)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).−21h10mkevAttacks confirmed in the real world.
CVE-2026-108883ETK-2026-1274Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
11 Oct 2026 • JeecgBoot <= 3.9.5
no check availablenot proven exploitable
8d 09h 11msince last run(AI 50m)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).+0mkevAttacks confirmed in the real world.
CVE-2026-108700ETK-2026-1273Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
11 Oct 2026 • 1Panel-dev CordysCRM < 1.9.2
no check availablenot proven exploitable
9d 10h 08msince last run(AI 1h 09m)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).+0mkevAttacks confirmed in the real world.
CVE-2026-12227ETK-2026-1272Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
8 Oct 2026 • visualcomposer visual_composer_website_builder <= 45.16.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.
+18dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI <1m)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).+18dkevAttacks confirmed in the real world.+14d
ETK-2026-1270Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
9 Oct 2026 • pip:turbohtml >= 1.1.0, <= 1.13.1
no check availablenot proven exploitable
9d 09h 16msince last run(AI 17m)Analysis: how long the AI spent reversing this signal.
cvss7.5awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−12dkevAttacks confirmed in the real world.
ETK-2026-1269Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
9 Oct 2026 • pip:pyload-ng >= 0.5.0b3.dev1, <= 0.5.0b3.dev101
no check availablenot proven exploitable
9d 09h 21msince last run(AI 22m)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).−12dkevAttacks confirmed in the real world.
CVE-2026-108708ETK-2026-1267Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
11 Oct 2026 • WuKongOpenSource Wukong_HRM
no check availablenot proven exploitable
9d 10h 48msince last run(AI 29m)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).+0mkevAttacks confirmed in the real world.
CVE-2026-108963ETK-2026-1261Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
11 Oct 2026 • David-Crty databasement >= 1.0.0, < 1.8.2
no check availablenot proven exploitable
9d 10h 47msince last run(AI 16m)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).+0mkevAttacks confirmed in the real world.
CVE-2026-107212ETK-2026-1237Zero'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 • go:github.com/xuri/excelize/v2 >= 2.1.0, < 2.11.1-0.20260930021559-01a9ff32fb3c
no check availablenot proven exploitable
9d 10h 33msince last run(AI 11m)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).+23h21mkevAttacks confirmed in the real world.
CVE-2026-108707ETK-2026-1231Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
11 Oct 2026 • WuKongOpenSource Wukong_HRM
no check availablenot proven exploitable
9d 09h 44msince last run(AI 1h 05m)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).+0mkevAttacks confirmed in the real world.
ETK-2026-1229Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
9 Oct 2026 • go siyuan >= 2.10.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.
−10dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.and counting(AI 42m)Analysis: how long the AI spent reversing this signal.
cvss7.0awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−12dkevAttacks confirmed in the real world.