Skip to content

$ZERODAY

Software holes under attack

3616.3% downon the month before

flaws in Oct 2026Up 200% from 12 in Oct 2022

Normal. 36 flaws in Oct 2026, down 16.3% on the month before.

From Oct 2024 to Oct 2026.

How it is counted

Normal17 to 29
Highest43Sep 2026
Unusual months0
Counts
Software flaws the US Cybersecurity and Infrastructure Security Agency added in a month to its catalog of flaws attackers are known to be using. Counted from December 2021, the first full month after the catalog's first load.
Why it is here
The government's own list of doors already being kicked in.
Source
CISA, Known Exploited Vulnerabilities catalog
Terms
US government work, public domain.
Cadence
Monthly. CISA adds entries any day; a month prints once it has ended. Newest complete month Oct 2026. Read Nov 12, 22:40 UTC.
Baseline
The prior 24 months, 12 needed.

Quote this number

CISA added 36 flaws to its catalog of known exploited vulnerabilities in Oct 2026, according to Tickerz, which counts the catalog.
Source: Tickerz $ZERODAY (Software holes under attack), from CISA, Known Exploited Vulnerabilities catalog.tickerz.com/x/zeroday

Asked often

How many software vulnerabilities are being exploited right now?
36 software flaws were added in Oct 2026 to the US Cybersecurity and Infrastructure Security Agency's catalog of flaws attackers are known to be using.
Where does the $ZERODAY number come from?
Tickerz reads it from CISA, Known Exploited Vulnerabilities catalog. Monthly. CISA adds entries any day; a month prints once it has ended. Each number is kept as it was first published, with a timestamped proof, and any later revision is shown beside it.
Can I download the $ZERODAY data?
Yes, free and with no key: the full history as JSON at https://tickerz.com/api/indices/zeroday and every period as CSV at https://tickerz.com/api/indices/zeroday/history.csv.

List it

No listing kit for $ZERODAY yet. A kit sets its strikes from 14 published numbers. This index publishes one a month and has none yet.

Resolution

Index
$ZERODAY Software holes under attack. Rulebook v0.2, 2026-10-04.
Prints
Monthly. CISA adds entries any day; a month prints once it has ended. The newest complete month is on the record after the daily proof at 12:40 UTC.
As first published

Oct 2026 is not timestamped yet. The daily proof at 12:40 UTC adds it.

The number as first published is final for settlement. A revision by the source is shown beside it and never replaces it.

Fallback
A month stays open until it ends and the catalog is read. A month with no entries is 0. A month the catalog can never be read for is void.
Precision
Whole catalog entries whose date added falls in the month.
Cost to move
Not practical. An entry is added by CISA after it confirms attacks.
Grade
reference. A federal agency's own catalog, read in full. A venue can count it directly. CISA has removed an entry when its CVE was withdrawn, which lowers a month already printed; the record keeps the revision.
For a rulebook
Settle on the number Tickerz first recorded for $ZERODAY for the month named in the contract, published at tickerz.com/x/zeroday and in GET /api/indices/zeroday, timestamped daily in Bitcoin with OpenTimestamps.

As first published

None on file yet.

Embed

Theme
Size

Badge

$ZERODAY on Tickerz

Card

Card, iframe
<iframe src="https://tickerz.com/embed/zeroday" title="$ZERODAY on Tickerz" width="480" height="200" style="border:0;max-width:100%" loading="lazy" allow="clipboard-write"></iframe>

Proof and data

Proof
Every reading is timestamped in Bitcoin once a day, so nobody can change it later. The newest proof covers Nov 12, in Bitcoin block 975,557.Proof fileLive feedHow it works
Data
The full history, free, no key.JSONCSVAPI docs

Name a number

Name a number you want counted. Within 48 hours it is a ticker, or you get the plain reason it cannot be built. Answers