Analyzing update patterns and velocity across 318,228 CVE records
| Updates | Count | Percentage |
|---|
The following CVEs have received the most updates since their initial publication:
| Rank | CVE ID | CNA | Updates | Last Updated | Update History |
|---|
Analyzing time elapsed between CVE publication and metadata update (cveMetadata.dateUpdated) to understand response patterns and maintenance practices.
Distribution of time elapsed from CVE publication to metadata update, showing response patterns across different time windows.
These CVEs experienced the longest delays between publication and their most recent metadata update timestamp, providing insights into extended maintenance cycles:
| Rank | CVE ID | CNA | Published | First Updated | Time to Update | Update History |
|---|---|---|---|---|---|---|
| 1 | CVE-1999-0035 | mitre | 1999-09-29 | 2025-10-20 | 26 years, 22 days | View |
| 2 | CVE-1999-0159 | mitre | 1999-09-29 | 2025-08-27 | 25 years, 333 days | View |
| 3 | CVE-1999-0468 | mitre | 1999-09-29 | 2025-08-25 | 25 years, 331 days | View |
| 4 | CVE-1999-0012 | mitre | 1999-09-29 | 2025-04-09 | 25 years, 193 days | View |
| 5 | CVE-1999-0011 | mitre | 1999-09-29 | 2025-04-09 | 25 years, 193 days | View |
| 6 | CVE-1999-0472 | mitre | 1999-09-29 | 2025-03-17 | 25 years, 170 days | View |
| 7 | CVE-1999-0103 | mitre | 1999-09-29 | 2025-03-17 | 25 years, 170 days | View |
| 8 | CVE-1999-0016 | mitre | 1999-09-29 | 2025-03-17 | 25 years, 170 days | View |
| 9 | CVE-1999-0532 | mitre | 2000-02-04 | 2025-03-17 | 25 years, 42 days | View |
| 10 | CVE-1999-0524 | mitre | 2000-02-04 | 2025-03-17 | 25 years, 42 days | View |
Cumulative distribution showing the fraction of CVEs at or below each update count.
Monthly commit activity with 12-month rolling average.
Update frequency distribution on a logarithmic scale for better visibility of outliers.
cveMetadata.dateUpdated value with the latest Git commit timestamp for that file.git log across the cves/ tree for speed; use --indepth for authoritative per-file history (slower).dateUpdated is later than the latest Git commit by more than the configured tolerance (default 3600 seconds), or when an internal date exists but no Git history is found for a file.updates = max(0, totalGitCommits - 1), so 0 means the CVE JSON was created and never changed afterwards.