validatingCVE-2026-969018m
ETK-2026-87waiting for further signals+20mETK-2026-86waiting for further signals+18mETK-2026-85waiting for further signals+16mETK-2026-84check available+13mCVE-2026-103099waiting for further signals+54mCVE-2026-103100check available+14mCVE-2026-103108waiting for further signals+25mCVE-2026-103111check available+24mCVE-2026-102911waiting for further signals+8mCVE-2026-103104waiting for further signals+1h 12m

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% validated993 of 2,2447% before t=0
1,500 of 2,244 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 22m
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 2,243 entries
listcard
ETK-2026-87Zero'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 • other AiSOC >= 7.2.0, <= 11.2.0
no check availablenot proven exploitable
3d 04h 08msince last run(AI 20m)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).−22dkevAttacks confirmed in the real world.cvss9.0
ETK-2026-86Zero'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 • other:beenuar/AiSOC <= 12.3.0
no check availablenot proven exploitable
2d 22h 02msince last run(AI 18m)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.cvss8.1
ETK-2026-85Zero'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 • pip:aisoc-actions <= 0.1.0
no check availablenot proven exploitable
3d 10h 07msince 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).kevAttacks confirmed in the real world.cvss8.5
ETK-2026-84Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
29 Sep 2026 • pip:aisoc-actions <= 12.3.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.
−21dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.and counting(AI 13m)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).kevAttacks confirmed in the real world.cvss9.6
CVE-2026-103099ETK-2026-83Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
30 Sep 2026 • Pexip Infinity >= 18.0.0, < 41.1.0
no check availablenot proven exploitable
16d 17h 19msince last run(AI 54m)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.cvss7.5
CVE-2026-103100ETK-2026-82Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
30 Sep 2026 • Pexip Infinity < 40.1.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.
+4.0dTTVTime-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.
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.cvss7.5
CVE-2026-103108ETK-2026-81Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
30 Sep 2026 • Pexip Infinity < 38.2.0; 39.0.0; 39.1.0; 40.0.0
no check availablenot proven exploitable
18d 20h 48msince 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).kevAttacks confirmed in the real world.cvss7.5
CVE-2026-103111ETK-2026-80Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
30 Sep 2026 • PCRE PCRE2 <=10.48
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
+1h25mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 24m)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.cvss7.6
CVE-2026-102911ETK-2026-79Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
30 Sep 2026 • zosmaai pi-llm-wiki 0.11.0; 0.11.1; 0.11.2; 0.11.3; 0.11.4; 0.11.5; 0.11.6; 0.11.7
no check availablenot proven exploitable
9d 07h 23msince 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).+0mkevAttacks confirmed in the real world.cvss9.4
CVE-2026-103104ETK-2026-78Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
30 Sep 2026 • Pexip Infinity < 38.2.0; 39.0.0; 39.1.0; 40.0.0
no check availablenot proven exploitable
17d 03h 29msince last run(AI 1h 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).kevAttacks confirmed in the real world.cvss7.5
CVE-2026-103109ETK-2026-77Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
30 Sep 2026 • Pexip Infinity < 38.2.0; 39.0.0; 39.1.0; 40.0.0
no check availablenot proven exploitable
20d 01h 20msince last run(AI 29m)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.cvss7.7
CVE-2026-103110ETK-2026-76Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.
30 Sep 2026 • Pexip Infinity < 38.2.0; 39.0.0; 39.1.0; 40.0.0
no check availablenot proven exploitable
19d 21h 06msince last run(AI 1h 04m)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-100661ETK-2026-75Zero'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 • maven:io.netty:netty-codec-http3 >= 4.2.0.Final, <= 4.2.17.Final
no check availablenot proven exploitable
3d 09h 20msince last run(AI 32m)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.cvss7.5
CVE-2026-103101ETK-2026-74Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
30 Sep 2026 • Pexip Infinity >= 30.0.0, < 41.0.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.
+1h36mTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 46m)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.6
CVE-2026-103102ETK-2026-73Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.
30 Sep 2026 • Pexip Infinity < 41.0.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.
+2.6dTTVTime-to-Validate: how long it takes Zero to confirm a signal is exploitable, from first ingestion.(AI 27m)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.6