Skip to content
StrikeCyberStrikeCyber
Field Manual · Concept

CVE

Reviewed November 14, 2026Concept 2 min read

Quick answer

A CVE (Common Vulnerabilities and Exposures) is a public identifier for one specific known security flaw, written like CVE-2025-61624. The ID lets vendors, scanners and security teams refer to the same vulnerability. A CVE on its own says nothing about severity; scores such as CVSS and EPSS, and lists such as CISA's KEV catalog, help decide what to fix first.

On this page

Every week brings hundreds of new CVEs. Treating them all as urgent is impossible, and ignoring them is how most breaches start. Understanding what a CVE is, and what it is not, is the first step to patching what matters.

01

How It Works

When a flaw is found in a product, a CVE Numbering Authority assigns an ID in the format CVE-year-number, and a short public description is published. National databases such as NIST's NVD then add details: affected versions, a CVSS severity score and references to vendor advisories.

SignalWhat it tells youWhere it comes from
CVE IDWhich specific flawCVE Program and CNAs
CVSS score (0 to 10)How severe the flaw could be in theoryNVD and vendors
EPSS score (0 to 100%)The chance it will be exploited in the next 30 daysFIRST
KEV listingIt is confirmed as exploited in the wildCISA
Vendor advisoryThe fix and workaroundsThe vendor
02

Why It Matters

Severity scores alone mislead: a large share of "critical" CVEs are never exploited, while some "medium" ones are used in ransomware attacks within days. Organizations that patch by CVSS alone spend effort on the wrong things. The CVEs that matter most are those that are exploited, internet-facing in your environment, and on systems that lead somewhere valuable.

03

How to Test for It

  1. Keep an accurate inventory of internet-facing systems and their software versions.
  2. Match that inventory against new CVEs, starting with those in the KEV catalog and with high EPSS scores.
  3. Confirm exposure: a vulnerable version is not always reachable or exploitable as configured.
  4. Use penetration testing to prove which vulnerabilities actually lead to compromise.
04

How to Reduce the Risk

Patch exploited and internet-facing CVEs first, within days rather than the usual monthly cycle, then work through the rest by EPSS and business impact. Watch the Threat Radar for newly exploited vulnerabilities, subscribe to your vendors' advisories, and retest after patching to confirm the fix worked.

05

Regulatory and Framework Context

For US organizations, CISA's Binding Operational Directive 22-01 requires federal agencies to fix KEV-listed CVEs by set deadlines, and many private organizations follow the same model. NIST's NVD publishes CVSS scores and details for each CVE.

Latest intel on this topic

Updated hourly from the daily briefing.

Common questions

Who assigns CVE numbers?

The CVE Program, run by MITRE with funding from the US government, coordinates CVE IDs. Hundreds of CVE Numbering Authorities (CNAs), including major vendors such as Microsoft, Google and Cisco, assign IDs for flaws in their own products.

How many CVEs are published each year?

Tens of thousands. More than 40,000 were published in 2024, and the number keeps rising, which is why prioritization matters more than trying to patch everything at once.

Is every CVE dangerous?

No. Only a small share of published CVEs are ever exploited in the wild. CISA's Known Exploited Vulnerabilities catalog lists those confirmed as exploited, and our Threat Radar tracks them hourly.

What is the difference between a CVE and a zero-day?

A zero-day is a flaw attackers exploit before a fix is available or before the vendor knows about it. Most zero-days receive a CVE ID once they are disclosed.

Change log

  1. November 14, 2026First published.
(877) 657-8496