04 · Dataset · Breaches

Breach data — what all those vulnerabilities actually turn into

Disclosure counts measure what gets found. Breach data measures what gets through. Three reputable series — ITRC's US compromise counts, Verizon's DBIR breach analysis, and IBM's cost report — each measuring something different, none of them a census. The sharpest vulnerability-relevant signal in any of them: the share of DBIR breaches that start with an exploited vulnerability has risen in each edition since 2023, and in 2026 it overtook stolen credentials for the first time in the report's 19-year history.

3,322
US data compromises in 2025
ITRC record, +5% on 2024
~31%
of breaches start with a vuln
DBIR 2026 — #1 vector, first time ever
$4.99M
global avg breach cost, 2026
+12% on 2025; US $11.5M
~1.7B
victim notices in 2024
six mega-breaches were 85% of them; ~279M in 2025

US data compromises per year (ITRC), 2016–2025

Publicly reported US data compromises, from the Identity Theft Resource Center's annual reports. Through 2019 ITRC counted data breaches; from 2020 it counts compromises (breaches, exposures and unknowns), so the line is roughly trend-comparable across the seam but not identical. 2026 is excluded from the line — only Q1 (780 compromises) is published; see the table.

The step-change is 2023: from a 1,100–1,900 band to 3,205, and it held: 3,158 in 2024 (just below 2023), a record 3,322 in 2025. Note the same caution as the CVE curve: ITRC counts reported compromises, so disclosure laws and reporting culture inflate the trend alongside actual intrusions. ITRC annual data breach reports, 2016–2025

The vulnerability connection — the one breach trend this site exists for

Breaches that began with vulnerability exploitation

Share of confirmed breaches whose initial access vector was exploiting a vulnerability, per Verizon DBIR edition.

~5% → 14% → 20% → ~31% in four editions. 2024's near-tripling was the MOVEit/zero-day year; 2026 is the first edition where vulns beat credentials as the way in. Verizon DBIR 2023–2026

Why this matters here

Everything else on this site counts vulnerability disclosure — which is rising for structural reasons that say little about risk. This is the number that connects disclosure to consequence: attackers are increasingly getting in through unpatched vulnerabilities rather than stolen passwords.

The patching side slowed too: DBIR 2026 reports median time-to-patch rose from 32 to 43 days. Separately, Mandiant reports exploitation within days on average (the clock story). The two are measured on different populations, so their difference is an illustration of the gap, not a measured exposure window.

Caveat: DBIR percentages describe DBIR's contributed caseload, and the contributor panel changes between editions. The shares rose within those changing samples; how much of that holds for all breaches is uncertain.

The DBIR series, edition by edition

Verizon's Data Breach Investigations Report analyzes incidents contributed by a changing roster of partners — raw counts swing with the contributor base, so read the vector percentages, not the totals, as trend. Editions before 2021 aren't shown: their counts couldn't be verified against a primary page for this build, and this site doesn't publish unverified numbers.

EditionIncidentsConfirmed breachesVuln-exploit vectorNote
2021 29,207 5,258 — Secondary-source (2021 DBIR PDF mirror); approximate.
2022 23,896 5,212 — Secondary coverage. 82% of breaches involved the human element.
2023 16,312 5,199 ~5% Incident count dropped vs 2022 — scoping change, not a real decline. Ransomware ~24% of breaches.
2024 30,458 10,626 14% Vuln exploitation as initial access nearly TRIPLED (+180% YoY) to 14% — the MOVEit/zero-day year.
2025 ~22,000 12,195 20% Verizon's release: 'over 22,000 security incidents, including 12,195 confirmed data breaches'. Vuln exploitation was the initial access vector in 20% of breaches (14% in the 2024 edition); Verizon reports exploitation itself up 34%, a different measure from the share; third-party involvement doubled 15%→30%; ransomware in 44% of breaches.
2026 ~31,000 ~22,000 ~31% FIRST TIME in the DBIR's 19-year history that vulnerability exploitation (~31%) overtook stolen credentials as the #1 breach entry point. Counts reported rounded ('~31,000 incidents', 'over 22,000 breaches'). Median time-to-patch rose 32→43 days. Published May 2026. Breaches involving a third party: 48% of all breaches (Verizon release).
Dimmed rows are secondary-sourced (medium confidence). 2026 counts are reported rounded by Verizon. full data: the breach dataset, in Substrate

Global average cost of a breach (IBM), 2017–2026

IBM / Ponemon Cost of a Data Breach report, global average in USD millions. 2016 omitted (inferred-only).

A slow grind up ($3.62M → $4.88M), then 2025's twist: the global average fell 9% — first decline in five years, credited to faster containment — while the US average rose 9% to a then-record $10.22M. In 2026 the global average was $4.99M (+12% on 2025). IBM Cost of a Data Breach 2017–2026

The ITRC dataset, year by year

YearCompromisesImpactNote
2016 1,093 36.6M records exposed Then all-time record; +40% over 2015. ITRC+CyberScout era.
2017 1,579 178M records exposed (approx) New record; +44.7% over 2016. Later ITRC datasets sometimes restate as 1,506/1,632. (Proofpoint secondary dropped 2026-10-20: it covers Jan–Oct 2017 only.)
2018 1,257 471M records exposed Marriott/Starwood alone = 383M records. ITRC internal inconsistency: 1,244 in key findings vs 1,257 restated in the 2019 report.
2019 1,473 165M records exposed +17% breaches over 2018; records exposed −65%. Last full year before the methodology change.
2020 1,108 301M victim notices 1,108 compromises (1,473 in 2019, a 25% fall); 300,562,519 individuals impacted. Methodology-break year: ITRC moved from records exposed to individuals impacted, so the 2020 impact figure is not comparable with 2019's 164,683,455 records. Source: ITRC's own release via archive.org (live page blocks scripted fetches).
2021 1,862 294M victim notices (approx) Then-record; +68% over 2020; broke the 2017 record. Restated 1,860 in later reports.
2022 1,802 422M victim notices 60 short of the 2021 record (restated 1,801). Quiet H1 (Russia/Ukraine war, crypto volatility). Only 34% of notices disclosed an attack vector.
2023 3,205 353M victim notices RECORD — +78% over 2022, +72% over the prior record. Restated 3,202 in later reports. Victims DOWN 16% vs 2022.
2024 3,158 1.70B victim notices (approx) −1% vs 2023, 44 events short of the record (restated 3,152). Victim notices ~1.7B, about 4.8x the 353M reported for 2023 here (ITRC's release states +312%, which does not reproduce from the as-originally-reported 2023 figure); six mega-breaches accounted for 85% of victim notices (Pomerium summary of the ITRC report).
2025 3,322 279M victim notices NEW RECORD — +5% vs 2024. Victim notices ~279M, far below 2024's ~1.7B. 70% of notices lacked attack info. Financial Services overtook Healthcare as #1 industry.
2026* 780 140M victim notices (approx) Q1 only (Jan–Mar). Full H1 2026 report not yet published as of 2026-07-21. Q1: ~140M victim notices; Under Armour 72.7M, SoundCloud 29.8M. 79% of Q1 notices lacked actionable info.
* 2026 is Q1 only — the full H1 report wasn't published as of this build. The impact column deliberately switches units at 2020: ITRC changed methodology from "records exposed" to "victim notices," and the two aren't comparable — so this site never draws them as one line. Victim notices count notices, not unique people. ITRC full data: the breach dataset, in Substrate

What breach data does and doesn't say about the AI question

The breach series shows the same 2023–2026 acceleration the disclosure data shows — compromise counts stepped up 78% in 2023, dipped 1% in 2024, and set a new record in 2025, and vuln-exploitation's share of breach entry tripled-then-doubled across the same window. What none of these sources establish is AI as the cause: ITRC's 2023 jump predates capable AI vuln-discovery tools, DBIR attributes its vector shift to zero-day supply-chain campaigns (MOVEit) and slowing patch cadence, and 70% of 2025 breach notices didn't disclose an attack vector at all. The correlation is real, documented, and — like everything else here — not yet attribution. The AI Question →