validatingCVE-2026-1141356m
CVE-2026-97698waiting for further signals+29mCVE-2026-97699waiting for further signals+16mETK-2026-2053check available+22mCVE-2026-111408check available+1h 06mCVE-2026-80344waiting for further signals+19mCVE-2026-108771waiting for further signals+2h 22mCVE-2026-80343check available+30mCVE-2026-80312waiting for further signals+15mCVE-2026-78162check available+13mCVE-2026-76994waiting 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,017 of 2,3067% before t=0
1,500 of 2,306 drawn
CVE-2026-113386
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 15m
How fast Zero starts validating it
step 3
validated
+4h 45m
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,306 entries
listcard
CVE-2026-97698ETK-2026-2055Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
19 Oct 2026 • pip:mistune < 3.3.4
no check availablenot proven exploitable
2d 08h 03msince 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).−2.4dkevAttacks confirmed in the real world.cvss7.5
CVE-2026-97699ETK-2026-2054Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
19 Oct 2026 • pip:mistune < 3.3.4
no check availablenot proven exploitable
2d 08h 40msince last run(AI 16m)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).−2.4dkevAttacks confirmed in the real world.cvss7.5
ETK-2026-2053Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
19 Oct 2026 • pip:mistune >= 3.3.0, < 3.3.4
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.4dTTVTime-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).−2.4dkevAttacks confirmed in the real world.cvss7.5
CVE-2026-111408ETK-2026-2052Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
19 Oct 2026 • ExpressTech Quiz And Survey Master <= 11.2.7
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+3h12mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 1h 06m)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-80344ETK-2026-2051Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
19 Oct 2026 • Apache Software Foundation Apache Camel >= 4.0.0, < 4.18.5; >= 4.19.0, < 4.22.1
no check availablenot proven exploitable
2d 06h 33msince last run(AI 19m)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).+1h03mkevAttacks confirmed in the real world.cvss8.2
CVE-2026-108771ETK-2026-2050Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
19 Oct 2026 • Apache Software Foundation Apache Kylin >= 4.0.0, <= 5.0.4
no check availablenot proven exploitable
2d 07h 14msince last run(AI 2h 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).kevAttacks confirmed in the real world.
CVE-2026-80343ETK-2026-2049Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
19 Oct 2026 • Apache Software Foundation Apache Camel >= 4.0.0, < 4.18.5; >= 4.19.0, < 4.22.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.
+1h04mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 30m)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).−23h46mkevAttacks confirmed in the real world.cvss8.2
CVE-2026-80312ETK-2026-2048Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
19 Oct 2026 • Apache Software Foundation Apache Camel >= 4.11.0, < 4.18.5; >= 4.19.0, < 4.22.1
no check availablenot proven exploitable
2d 08h 32msince last run(AI 15m)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).+48mkevAttacks confirmed in the real world.cvss8.2
CVE-2026-78162ETK-2026-2047Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
19 Oct 2026 • Apache Software Foundation Apache Camel >= 4.0.0, < 4.18.5; >= 4.19.0, < 4.22.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.
+1h00mTTVTime-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.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−3.0dkevAttacks confirmed in the real world.cvss10.0
CVE-2026-76994ETK-2026-2046Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
19 Oct 2026 • Apache Software Foundation Apache Answer <= 2.0.2
no check availablenot proven exploitable
2d 09h 40msince last run(AI 19m)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.
CVE-2026-96759ETK-2026-2045Zero'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 • npm:orval <= 8.27.0
no check availablenot proven exploitable
2d 10h 00msince 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).kevAttacks confirmed in the real world.cvss9.8
CVE-2026-110887ETK-2026-2044Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
19 Oct 2026 • HivePress <= 1.7.32
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 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.cvss9.9
CVE-2026-96758ETK-2026-2043Zero'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 • npm:orval <= 8.27.0
no check availablenot proven exploitable
2d 10h 18msince last run(AI 20m)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.8
CVE-2026-96755ETK-2026-2042Zero'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 • npm:orval <= 8.27.0
no check availablenot proven exploitable
2d 10h 47msince last run(AI 35m)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).−17dkevAttacks confirmed in the real world.cvss10.0
CVE-2026-13695ETK-2026-2041Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
19 Oct 2026 • Integratec all versions
no check availablenot proven exploitable
2d 08h 33msince last run(AI 7m)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