<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/mitre-acknowledges-inaccurate-publication-timestamps-in-87-of-its-recent-cve-records-jhyynzy97" -->

---
title: MITRE Acknowledges Inaccurate Publication Timestamps in...
description: MITRE has acknowledged that a legacy publishing system causes inaccurate timestamps on thousands of CVE records. Researcher Jerry Gamblin found 87% of MITRE's...
canonical: https://daily.dev/posts/mitre-acknowledges-inaccurate-publication-timestamps-in-87-of-its-recent-cve-records-jhyynzy97
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: MITRE Acknowledges Inaccurate Publication Timestamps in 87% of Its Recent CVE Records | daily.dev
og:description: MITRE has acknowledged that a legacy publishing system causes inaccurate timestamps on thousands of CVE records. Researcher Jerry Gamblin found 87% of MITRE's...
og:url: https://daily.dev/posts/mitre-acknowledges-inaccurate-publication-timestamps-in-87-of-its-recent-cve-records-jhyynzy97
og:image: https://api.daily.dev/og/posts/JhyyNzy97.png
og:image:alt: MITRE Acknowledges Inaccurate Publication Timestamps in 87% of Its Recent CVE Records
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# MITRE Acknowledges Inaccurate Publication Timestamps in 87% of Its Recent CVE Records

**[Socket](https://daily.dev/sources/socketdev)** · 6 min read · 1 upvotes · 0 comments

## Summary

MITRE has acknowledged that a legacy publishing system causes inaccurate timestamps on thousands of CVE records. Researcher Jerry Gamblin found 87% of MITRE's 4,509 CVEs from the past 52 weeks carried a publication time of exactly 00:00:00.000Z, while none of the 100,235 records from 425 other CNAs did. Comparing timestamps to the official change log, he found that for 144 midnight-stamped records in a 202-record sample, the median gap to first appearance was 15.8 hours, versus a median of 4.6 minutes for MITRE's other records. MITRE's Alec Summers attributed this to a legacy API client that needs a fixed time value for system stability, and said publications using that architecture will be phased out in Q1 2027; MITRE has not prioritized correcting historical timestamps.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://socket.dev/blog/mitre-cve-timestamp-issues>

## Questions this post answers

### Why do so many MITRE CVE records show a publication time of exactly midnight UTC?

MITRE's legacy publishing client requires a time value but faces concurrency issues, so it defaults to a single predictable value of 00:00:00 for system stability, according to MITRE's CVE/CWE Project Leader Alec Summers. Researcher Jerry Gamblin found 87% of MITRE's 4,509 CVEs over a 52-week period carried this exact midnight timestamp, versus 0% among 100,235 records from 425 other CNAs.

_Anyone measuring vulnerability disclosure timing tracks data quality fixes like this one on daily.dev._

### How much error do MITRE's midnight CVE timestamps introduce when measuring publication delay?

Midnight-stamped MITRE records showed a median 15.8-hour gap between their recorded publication time and their actual first appearance in the CVE List's change log, based on 144 of 202 records examined from October 19 to November 16. Correctly timestamped MITRE records and records from other CNAs showed a median delay of only about 4.5 to 4.6 minutes.

_Researchers comparing CNA disclosure latency can follow data-quality caveats like this on daily.dev._

### When will MITRE fix the midnight timestamp bug in its CVE records?

MITRE plans to phase out the legacy publishing architecture responsible for the midnight timestamps in the first quarter of 2027, per Alec Summers, MITRE's CVE/CWE Project Leader. The transition is already underway: 97% of MITRE records from 2023 through 2025 carried midnight timestamps, compared with 66% of records published in the fourth quarter of 2026. Historical timestamps will not be corrected.

_Teams tracking CVE data reliability over time can watch for this kind of fix timeline on daily.dev._

## Similar posts on daily.dev

- [The CVE spike across major software companies is a remediation problem](https://daily.dev/posts/the-cve-spike-across-major-software-companies-is-a-remediation-problem-eirfbzfqc) · Aikido Security · 0 upvotes · 0 comments
- [November CVEs Fell 25% YoY, Driven by Slowdowns at Major CNA...](https://daily.dev/posts/november-cves-fell-25-yoy-driven-by-slowdowns-at-major-cna--og1jf6p4g) · Socket · 0 upvotes · 0 comments
- [This year’s bug count just passed 100K](https://daily.dev/posts/this-year-s-bug-count-just-passed-100k-lpxnhl9mk) · The Register · 3 upvotes · 0 comments
- [What Zero-Day Response Should Be in the Post-Mythos Era](https://daily.dev/posts/what-zero-day-response-should-be-in-the-post-mythos-era-sy5pwxui7) · BleepingComputer · 0 upvotes · 0 comments
- [How LLMs Are Compressing Attacker MTTE, and What Defenders Need to Do About It](https://daily.dev/posts/how-llms-are-compressing-attacker-mtte-and-what-defenders-need-to-do-about-it-lvvtd5lwi) · Security Boulevard · 3 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security), [#data-quality](https://daily.dev/tags/data-quality)

[View this post on daily.dev](https://daily.dev/posts/mitre-acknowledges-inaccurate-publication-timestamps-in-87-of-its-recent-cve-records-jhyynzy97)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"MITRE Acknowledges Inaccurate Publication Timestamps in 87% of Its Recent CVE Records","url":"https://daily.dev/posts/mitre-acknowledges-inaccurate-publication-timestamps-in-87-of-its-recent-cve-records-jhyynzy97","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/mitre-acknowledges-inaccurate-publication-timestamps-in-87-of-its-recent-cve-records-jhyynzy97"},"datePublished":"2026-11-18T23:56:34.992Z","dateModified":"2026-11-19T02:14:04.732Z","description":"MITRE has acknowledged that a legacy publishing system causes inaccurate timestamps on thousands of CVE records. Researcher Jerry Gamblin found 87% of MITRE's...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/c8279a206b85bbbdfcdf0994b8b51245?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/c8279a206b85bbbdfcdf0994b8b51245?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Socket","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Socket","logo":"https://media.daily.dev/image/upload/s---oEn9czC--/f_auto/v1716187892/logos/socketdev","url":"https://daily.dev/sources/socketdev"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/mitre-acknowledges-inaccurate-publication-timestamps-in-87-of-its-recent-cve-records-jhyynzy97","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,data-quality","timeRequired":"PT6M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Socket","item":"https://daily.dev/sources/socketdev"},{"@type":"ListItem","position":3,"name":"MITRE Acknowledges Inaccurate Publication Timestamps in 87% of Its Recent CVE Records"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/mitre-acknowledges-inaccurate-publication-timestamps-in-87-of-its-recent-cve-records-jhyynzy97#faq","mainEntity":[{"@type":"Question","name":"Why do so many MITRE CVE records show a publication time of exactly midnight UTC?","acceptedAnswer":{"@type":"Answer","text":"MITRE's legacy publishing client requires a time value but faces concurrency issues, so it defaults to a single predictable value of 00:00:00 for system stability, according to MITRE's CVE/CWE Project Leader Alec Summers. Researcher Jerry Gamblin found 87% of MITRE's 4,509 CVEs over a 52-week period carried this exact midnight timestamp, versus 0% among 100,235 records from 425 other CNAs. Anyone measuring vulnerability disclosure timing tracks data quality fixes like this one on daily.dev."}},{"@type":"Question","name":"How much error do MITRE's midnight CVE timestamps introduce when measuring publication delay?","acceptedAnswer":{"@type":"Answer","text":"Midnight-stamped MITRE records showed a median 15.8-hour gap between their recorded publication time and their actual first appearance in the CVE List's change log, based on 144 of 202 records examined from October 19 to November 16. Correctly timestamped MITRE records and records from other CNAs showed a median delay of only about 4.5 to 4.6 minutes. Researchers comparing CNA disclosure latency can follow data-quality caveats like this on daily.dev."}},{"@type":"Question","name":"When will MITRE fix the midnight timestamp bug in its CVE records?","acceptedAnswer":{"@type":"Answer","text":"MITRE plans to phase out the legacy publishing architecture responsible for the midnight timestamps in the first quarter of 2027, per Alec Summers, MITRE's CVE/CWE Project Leader. The transition is already underway: 97% of MITRE records from 2023 through 2025 carried midnight timestamps, compared with 66% of records published in the fourth quarter of 2026. Historical timestamps will not be corrected. Teams tracking CVE data reliability over time can watch for this kind of fix timeline on daily.dev."}}]}
```

