Ubuntu — Security Activity Report

Canonical Ubuntu (USN advisories)

Generated Jun 13, 2026Cohort: 3 vendors with ≥10 CVE advisoriesMethodology ↗

CVE Disclosure Volume

Total all-time: 25,576 CVEs with Ubuntu advisories. Source: NVD CVE records joined with vendor advisory publish dates.

Severity Composition

↓ -6.8 pp

34.3% of Ubuntu's 25,576 CVEs are CRITICAL or HIGH severity. Industry median: 41.1%. Source: NVD CVSS v3.1.

CRITICAL 1,700 (6.6%)HIGH 7,084 (27.7%)MEDIUM 9,671 (37.8%)LOW 585 (2.3%)NONE 6,533 (25.5%)

CISA KEV Listings

↓ -0.1 pp

48 of 8,832 Ubuntu CVEs in the last 3 years are on CISA's Known Exploited Vulnerabilities catalog (0.5%). Industry median: 0.6%.

Source: CISA Known Exploited Vulnerabilities catalog (current snapshot). KEV listing means CISA observed active in-the-wild exploitation.

Vendor Patch Velocity

Insufficient data to publish a reliable patch-velocity metric for Ubuntu(sample size: 0, minimum required: 10).

Top Recurring Weakness Classes

Most-frequently mapped CWEs across Ubuntu's last 3 years of CVE disclosures. Source: NVD — CWE mapping per MITRE taxonomy.

CWE-476NULL Pointer Dereference1,116 CVEs
CWE-416Use After Free826 CVEs
CWE-787Out-of-bounds Write456 CVEs
CWE-125Out-of-bounds Read435 CVEs
CWE-401Missing Release of Memory after Effective Lifetime (Memory Leak)342 CVEs

Data sources & corrections

NVD National Vulnerability Database (nvd.nist.gov) — CVE records + CVSS v3.1 severity
MITRE cvelistV5 (github.com/CVEProject/cvelistV5) — CNA-published CVE timestamps
CISA Known Exploited Vulnerabilities catalog (cisa.gov/known-exploited-vulnerabilities-catalog)
Vendor security advisories (RHSA, USN, MSRC, GHSA, etc.) — published_at timestamps
MITRE CWE taxonomy (cwe.mitre.org) — weakness class mappings

Snapshot generated Jun 13, 2026. Industry medians refresh every 6 hours; raw vendor counts are queried live on each request.

Spot a factual error in this report?

Email support@echelongraph.io with the specific number you're disputing and a link to the authoritative source. We review every report and publish corrections on the methodology page.