CVE
Unique identifier assigned to a publicly known cybersecurity vulnerability, listed in a global database run by MITRE.

CVE (Common Vulnerabilities and Exposures) is a unique identifier assigned to each publicly known cybersecurity vulnerability. Run by the MITRE Corporation and funded by the US government, the CVE program is the global reference catalog of software flaws. Each CVE takes the form CVE-[year]-[sequential number] and is enriched with a CVSS severity score from 0 to 10. In 2023, 28,902 CVEs were published, an all-time record.
Technical definition
The life cycle of a CVE
A vulnerability may be discovered by a security researcher, a bug bounty program, an internal audit or active exploitation (zero-day). The finder reports the flaw to a CNA (CVE Numbering Authority), an organization accredited by MITRE (major software vendors, national CERTs, researchers). The CNA assigns a CVE identifier and coordinates responsible disclosure: the vendor usually has 90 days to release a fix before the CVE is published.
NIST's NVD (National Vulnerability Database) then enriches the CVE with the CVSS score, the affected products (CPE) and patch references. Vulnerability scanners (Nessus, Qualys, Snyk) query these databases to detect the CVEs present in a system.
CVSS scoring
CVSS (Common Vulnerability Scoring System) rates severity on a scale of 0 to 10 using three groups of metrics. The base score covers the attack vector (network, adjacent, local, physical), complexity, required privileges, required user interaction, and the impact on confidentiality, integrity and availability. A score of 8.8 (like OpenClaw's CVE-2026-25253) indicates a remotely exploitable flaw with minimal user interaction and high impact.
Current challenges
Exploding volume and prioritization
The number of published CVEs grows by 15-20% a year, outpacing the remediation capacity of most organizations. Only ~1% of CVEs are actually exploited (768 in 2024 according to VulnCheck), but security teams have to sort through thousands of reports. Modern approaches use EPSS (Exploit Prediction Scoring System), which predicts the probability of exploitation within 30 days, so effort can focus on the CVEs that carry real risk.
Impact on AI-generated code
Vibe coding amplifies CVE risk: LLM-generated code can reproduce vulnerable patterns found in its training data. Fast-growing projects like OpenClaw pile up CVEs because development speed outpaces security review capacity. In due diligence, the ratio of CVEs per month of project life becomes a useful indicator of the team's security maturity.
Standards and Specifications
CVSS (Common Vulnerability Scoring System)
System for rating vulnerability severity from 0.0 to 10.0
NVD (National Vulnerability Database)
US database that enriches CVEs with CVSS scores and metadata
CWE (Common Weakness Enumeration)
Classification of the types of software weaknesses behind CVEs
Frequently Asked Questions
How does the CVE system work?
The CVE program is run by the MITRE Corporation and funded by the US Department of Homeland Security. When a vulnerability is discovered, a CNA (CVE Numbering Authority), an authorized organization such as Google, Microsoft, Red Hat or an accredited researcher, assigns it a unique identifier in the format CVE-[year]-[number] (e.g. CVE-2026-25253).
The CVE record contains a description of the vulnerability, the affected products and references (advisories, patches). The CVSS severity score (0 to 10) is added by the NVD: Low (0.1-3.9), Medium (4.0-6.9), High (7.0-8.9), Critical (9.0-10.0). A CVE scored 8.8, like the OpenClaw one, is rated High, close to Critical.
Why do CVEs matter in due diligence?
CVEs are an objective indicator of a piece of software's security posture. In technical due diligence, the number of open CVEs, their severity and the time to fix them reveal the team's security maturity. A project that patches five CVEs in six days (the OpenClaw case, late January 2026), shows reactive rather than proactive management.
CVEs with public exploits are especially critical: they let anyone reproduce the attack. In an M&A context, unpatched critical CVEs can be a liability (remediation cost, breach risk, reputational impact) that must be factored into the valuation.
What is the difference between CVE, CWE and CVSS?
A CVE identifies a specific vulnerability in a given product (e.g. CVE-2026-25253 = remote code execution in OpenClaw). CWE classifies the underlying type of software weakness (e.g. CWE-79 = Cross-Site Scripting). CVSS rates severity from 0 to 10 using standardized criteria (attack vector, complexity, impact).
A single CWE can give rise to thousands of CVEs across different products. CVSS helps prioritize remediation: Critical CVEs (9.0+) should be patched within 24-48 hours and High ones (7.0-8.9) within 7 days, according to CISA recommendations.