validatingETK-2026-23253m
CVE-2026-85568waiting for further signals+36mCVE-2026-51904waiting for further signals+41mCVE-2026-51901waiting for further signals+46mCVE-2026-51899waiting for further signals+38mCVE-2026-103880waiting for further signals+12mCVE-2026-103885waiting for further signals+22mCVE-2026-105219waiting for further signals+30mCVE-2026-105210waiting for further signals+16mCVE-2026-105086waiting for further signals+56mCVE-2026-93019waiting for further signals+19m

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,008 of 2,2767% before t=0
1,500 of 2,276 drawn
CVE-2026-70197
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 18m
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 1,251 entries
listcard
CVE-2026-85568ETK-2026-599Zero'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 • Unlimited Elements for Elementor >= 1.5.139, < 2.0.21
no check availablenot proven exploitable
16d 14h 58msince last run(AI 36m)Analysis: how long the AI spent reversing this signal.
cvss6.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-51904ETK-2026-584Zero'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 • SuperAGI n/a
no check availablenot proven exploitable
16d 17h 59msince last run(AI 41m)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).kevAttacks confirmed in the real world.
CVE-2026-51901ETK-2026-583Zero'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 • SuperAGI n/a
no check availablenot proven exploitable
15d 10h 36msince last run(AI 46m)Analysis: how long the AI spent reversing this signal.
cvss8.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-51899ETK-2026-582Zero'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 • SuperAGI n/a
no check availablenot proven exploitable
15d 10h 48msince last run(AI 38m)Analysis: how long the AI spent reversing this signal.
cvss4.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-103880ETK-2026-579Zero'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 • Apache Software Foundation Apache Directory LDAP API >= 2.1.0, < 2.1.9
no check availablenot proven exploitable
16d 19h 14msince last run(AI 12m)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-103885ETK-2026-578Zero'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 • Apache Software Foundation Apache Directory LDAP API >= 2.1.0, < 2.1.9
no check availablenot proven exploitable
16d 19h 44msince last run(AI 22m)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-105219ETK-2026-574Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
4 Oct 2026 • mwilliamson mammoth.js >= 1.3.0, < 1.12.3
no check availablenot proven exploitable
16d 19h 08msince last run(AI 30m)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).kevAttacks confirmed in the real world.
CVE-2026-105210ETK-2026-572Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
4 Oct 2026 • zitadel < 4.17.1; < 3.4.15
no check availablenot proven exploitable
16d 21h 09msince last run(AI 16m)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-105086ETK-2026-570Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
4 Oct 2026 • WWBN AVideo >= 12.4, <= 29.2.0
no check availablenot proven exploitable
13d 13h 23msince last run(AI 56m)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-93019ETK-2026-569Zero'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 • cpan:Imager <=1.035
no check availablenot proven exploitable
16d 22h 14msince last run(AI 19m)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-102505ETK-2026-568Zero'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 • cpan:Imager 1.036
no check availablenot proven exploitable
16d 21h 54msince last run(AI 47m)Analysis: how long the AI spent reversing this signal.
cvss6.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-105213ETK-2026-565Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
4 Oct 2026 • zitadel < 4.17.1
no check availablenot proven exploitable
15d 15h 25msince last run(AI 55m)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-105211ETK-2026-564Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
4 Oct 2026 • zitadel < 4.17.1
no check availablenot proven exploitable
14d 20h 58msince last run(AI 18m)Analysis: how long the AI spent reversing this signal.
cvss9.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-105209ETK-2026-562Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
4 Oct 2026 • zitadel < 4.17.1; < 3.4.15
no check availablenot proven exploitable
16d 21h 45msince last run(AI 37m)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-105215ETK-2026-561Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
4 Oct 2026 • zitadel < 4.16.2; < 3.4.14
no check availablenot proven exploitable
13d 14h 12msince last run(AI 44m)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-51893ETK-2026-559Zero'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 • Ragflow n/a
no check availablenot proven exploitable
16d 23h 50msince last run(AI 1h 12m)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).kevAttacks confirmed in the real world.
CVE-2026-51896ETK-2026-558Zero'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 • Infiniflow Ragflow n/a
no check availablenot proven exploitable
16d 23h 50msince last run(AI 1h 17m)Analysis: how long the AI spent reversing this signal.
cvss6.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-51895ETK-2026-557Zero'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 • Ragflow n/a
no check availablenot proven exploitable
17d 01h 07msince last run(AI 56m)Analysis: how long the AI spent reversing this signal.
cvss6.5cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+1.8dkevAttacks confirmed in the real world.
CVE-2026-51892ETK-2026-556Zero'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 • Ragflow n/a
no check availablenot proven exploitable
14d 23h 29msince last run(AI 55m)Analysis: how long the AI spent reversing this signal.
cvss6.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-51894ETK-2026-554Zero'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 • Ragflow n/a
no check availablenot proven exploitable
17d 01h 59msince last run(AI 1h 20m)Analysis: how long the AI spent reversing this signal.
cvss6.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.