Safeguard
Industry Analysis•

Weakness classes in CISA KEV: memory, injection and authentication

Grouping KEV entries by CWE shows memory safety flaws at 22%, injection at 17% and authentication flaws at 13%, with authentication rising in 2026.

Safeguard Security Team
4 min read

Grouping the 1,748 CISA KEV entries by weakness type, memory safety flaws appear on 377 entries (22%), injection on 302 (17%) and authentication or access control flaws on 224 (13%). Memory safety peaked in 2022 and has fallen, while authentication flaws are the largest share of any year so far in 2026.

Method

We downloaded the KEV JSON on 19 October 2026 (version 2026.10.16). Each entry lists zero or more CWE identifiers in its cwes field. We built three groups by hand and counted an entry once per group if any of its CWEs fell in it.

  • Memory safety: CWE-787, 416, 119, 122, 125, 120, 121, 190, 415, 476, 123, 126, 401, 763, 762 and 824.
  • Injection: CWE-78, 77, 94, 89, 79, 74, 917, 95 and 91.
  • Authentication and access control: CWE-287, 306, 862, 863, 284, 288, 290, 798, 522, 269, 259, 639, 285, 250, 295 and 345.

The grouping is our judgment. A different list would shift the numbers, and an entry can sit in more than one group, so the three counts do not add up to a whole.

The whole catalog

GroupEntriesShare of 1,748
Memory safety37722%
Injection30217%
Authentication and access control22413%
Path traversal or file upload1227%
Deserialization (CWE-502)714%
No CWE listed17510%

The single most common CWE codes are CWE-20 improper input validation (119 entries), CWE-78 OS command injection (111), CWE-787 out of bounds write (105), CWE-416 use after free (93) and CWE-119 buffer errors (88).

How the mix has moved

Year addedEntriesMemoryInjectionAuthentication
2022555148 (27%)77 (14%)36 (6%)
202318746 (25%)39 (21%)30 (16%)
202418624 (13%)42 (23%)32 (17%)
202524542 (17%)46 (19%)36 (15%)
202626438 (14%)50 (19%)56 (21%)

Two things stand out. Memory safety fell from about a quarter of additions in 2022 and 2023 to roughly 13% to 17% since. And authentication flaws, which were 6% of 2022 additions, are 21% of 2026 additions so far.

One caution on 2022: the early catalog absorbed a backlog of older Windows, Office and browser bugs, which are mostly memory flaws. That probably inflates the early memory share.

What it means for a team

Memory flaws still matter, but the recent additions lean toward flaws that let an attacker skip login or run a command through a web or management interface. For code you write, that points at input handling and access checks on every route. For products you run, it points at keeping management interfaces off the open internet and patching them quickly.

If you use these shares to decide what to scan for, remember that KEV only lists flaws with known exploitation. It tells you what attackers used, not every weakness that exists.

Safeguard's SBOM and dependency scanning lists the components you run, and reachability analysis helps separate vulnerable code your application calls from code it does not. You can try a free scan at gold.safeguard.sh/scan.

Try it yourself

Click through it at your own pace, or open it full screen.

Run the scan and look at which findings fall under injection and access control.

Quick check

Does a CWE group tell me which flaws will be exploited next?

No. It describes the entries already in the catalog. Use it to guide what to review, not to forecast.

Why is the no-CWE count 175?

Some entries, mostly older ones, have no weakness code recorded in the catalog data.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.