kevmap

For a vulnerability being exploited right now, what do we actually know about detecting it?

kevmap joins CISA's Known Exploited Vulnerabilities catalogue to ATT&CK techniques, MITRE's detection strategies and log sources, and SigmaHQ rules — and shows, without guessing, where that chain breaks.

1748
CVEs in KEV (2026.10.16)
24.3%
424 have a public ATT&CK mapping
75.7%
1324 have none — from any public source
6
mapped under ATT&CK 16.1 to a technique since revoked or deprecated
20
of 152 mapped techniques have no Sigma rule
Mapped 418 Stale 6 Unmapped 1324

Mapped = 424 of 1748 (24.3%), from CTID Mappings Explorer pinned to KEV 2025-07-28 and ATT&CK 16.1, counting any mapping type. Counting only exploitation_technique: 410 (23.5%). Definitions.

357 CVEs have been added to KEV since the mapping snapshot of 2025-07-28. 0 of them have a mapping. The authoritative CVE → ATT&CK source is not keeping pace with the catalogue it describes. kevmap shows those entries as unmapped rather than filling the gap with inference — the obvious way to fill it produces noise.

What works: technique → detection

ATT&CK v20.0 publishes a detection strategy for 703 of 706 live techniques, through 1770 analytics naming 4206 concrete log source / channel pairs across 266 log sources. SigmaHQ adds 3323 rules tagged to 400 techniques. That half of the chain is dense, current and machine-checkable; the site traverses it exactly.

Browse by log source → · Browse techniques →

What is missing: CVE → technique

One public source maps KEV CVEs to ATT&CK: CTID's Mappings Explorer, 424 CVEs, last updated for KEV 2025-07-28 against ATT&CK 16.1. CISA's catalogue carries no technique field. CVE records carry CWE (1573 of 1748 KEV entries do) but CWE does not say how a thing is exploited, and the CAPEC bridge people use to pretend otherwise has not been updated since 2023-01-24.

The gap, by vendor, product and year →

Mapped but uncovered

Techniques that at least one KEV CVE maps to, for which MITRE publishes a detection strategy, and for which SigmaHQ has no rule. If you write detections, start here.

TechniqueTacticsKEV CVEsMITRE analytics
T1608.001 Upload Malwareresource development111
T1011 Exfiltration Over Other Network Mediumexfiltration43
T1497 Virtualization/Sandbox Evasionstealth, discovery43
T1037 Boot or Logon Initialization Scriptspersistence, privilege escalation35
T1573.001 Symmetric Cryptographycommand and control35
T1001 Data Obfuscationcommand and control23
T1499.002 Service Exhaustion Floodimpact24
T1530 Data from Cloud Storagecollection23
T1584.005 Botnetresource development21
T1592 Gather Victim Host Informationreconnaissance21
T1003.008 /etc/passwd and /etc/shadowcredential access11
T1071.002 File Transfer Protocolscommand and control15

All 20 →

Recently added to KEV

AddedCVEVendor / productStateSigma
2026-10-16CVE-2026-102764BeyondTrust Remote SupportUnmapped
2026-10-16CVE-2025-61624Fortinet Multiple ProductsUnmapped
2026-10-15CVE-2026-21589Atlassian Multiple ProductsUnmapped
2026-10-14CVE-2026-76519Cisco Secure Email GatewayUnmapped
2026-10-14CVE-2026-105134Ahsay AhsayCBSUnmapped
2026-10-14CVE-2026-105133Ahsay AhsayCBSUnmapped
2026-10-14CVE-2026-0322Palo Alto Networks PAN-OSUnmapped
2026-10-13CVE-2026-96951Microsoft WindowsUnmapped
2026-10-13CVE-2026-104935Ivanti Connect SecureUnmapped
2026-10-08CVE-2023-22894Strapi StrapiUnmapped
2026-10-08CVE-2021-3199ONLYOFFICE DocsUnmapped
2026-10-08CVE-2016-3081Apache StrutsUnmapped
2026-10-08CVE-2015-5477ISC BINDUnmapped
2026-10-08CVE-2015-3306ProFTPD ProFTPDUnmapped
2026-10-04CVE-2026-88779Citrix NetScalerUnmapped
2026-10-02CVE-2026-102490Zammad GmbH ZammadUnmapped
2026-10-02CVE-2026-102489Zammad GmbH ZammadUnmapped
2026-10-01CVE-2026-104286Fortinet FortiMailUnmapped
2026-09-30CVE-2026-76504Cisco Catalyst SD-WAN ManagerUnmapped
2026-09-29CVE-2026-86950Apple Multiple ProductsUnmapped

Last 7 days (2026-10-11 → 2026-10-17): 9 added to KEV, 0 with an ATT&CK mapping, 0 with Sigma coverage via a mapped technique. Changes over time →