Skip to content

Image: cdn.sanity.io · rights & removal

Executive Summary

MITRE has acknowledged that a legacy publishing system causes inaccurate timestamps in a significant portion of its CVE records. Research by Jerry Gamblin found that 87% of MITRE's CVEs published over the last year had a publication time recorded as exactly midnight UTC due to this legacy system. This system is slated for retirement in the first quarter of 2027.
The discrepancy arises because the legacy system used a standardized, fixed timestamp (midnight) for stability, which does not reflect the actual time vulnerabilities were published. Analysis showed that for records with inaccurate midnight timestamps, the delay between the recorded timestamp and the actual publication time was often significantly longer than measured delays in other vulnerability reporting authorities.
MITRE's explanation attributes the issue to historical differences in publishing infrastructure involving various API endpoints and concurrency issues in legacy client architecture. While MITRE confirmed the problem and a timeline for resolution, they indicated that modifying historical timestamps is not currently a priority, focusing instead on improving future data accuracy.

Facts Only

* 87% of MITRE's CVEs published over the past year had a publication time of exactly midnight UTC.
* A legacy publishing system is responsible for inaccurate timestamps in thousands of CVE records.
* The legacy system is scheduled to be phased out in the first quarter of 2027.
* Research analyzed 4,509 MITRE CVEs and found 3,901 (87%) had a datePublished timestamp of exactly 00:00:00.000Z.
* For the records with midnight timestamps, the median delay between the recorded time and first appearance in the change log was 15.8 hours.
* The remaining 58 MITRE records carried other publication times and showed a median delay of 4.6 minutes.
* Records from other CVE Numbering Authorities (CNAs) showed a comparable median delay of 4.5 minutes for non-midnight timestamps.
* MITRE publishes via the same CVE Services API used by other CNAs but uses different endpoints based on publishing workflows.
* 97% of MITRE records published from 2023 through 2025 carried midnight timestamps.

Full Take

The core issue identified is not a single error, but a systemic conflict between system stability and temporal accuracy within an aging infrastructure. The decision to use a fixed timestamp (midnight UTC) in a legacy system appears to be a function of maintaining architectural predictability during concurrent operations, rather than reflecting actual time-to-publish events. This creates a scenario where downstream metrics, such as measuring vulnerability disclosure latency, are built upon artifactual data that cannot reliably quantify real-world publication speeds across different entities.
The resistance to correcting historical timestamps, framed as not being a demonstrated priority need by consumers, suggests a prioritization of operational stability over retrospective perfect accuracy. This introduces an agency tension: the immediate need for system stability versus the long-term need for verifiable data integrity in security analysis. The 15.8-hour discrepancy highlights how structural decisions made for internal stability can impose significant, non-trivial uncertainty on external analytical processes that rely on time sequencing.
The pattern suggests that when systems prioritize monolithic architectural coherence, the cost is shifted to data consumers who must then develop complex compensating models to account for known systemic biases. The implication for human agency lies in recognizing that data quality itself is a feature shaped by system design choices, and achieving true insight requires actively demanding transparency regarding these foundational structural compromises rather than passively accepting the resulting noise.
Bridge Questions: If retrospective correction is not prioritized, what mechanisms can be established for post-hoc auditing of systems built on fixed timestamps? How should downstream analysis tools account for documented systemic temporal biases when calculating latency metrics across disparate authorities? What responsibility does an entity hold for ensuring foundational system decisions do not impose unquantifiable uncertainty on public vulnerability intelligence?

From the original · Socket Security Blog

MITRE acknowledges inaccurate publication timestamps in 87% of its recent CVE records and plans to retire the legacy system responsible in 2027. - Sarah Gooding MITRE has acknowledged that a legacy publishing system is responsible for inaccurate timestamps in thousands of CVE records, following research showing that 87% of the organization's CVEs published over the past year were assigned a…
Read the full story at socket.dev

Sentinel unavailable

The automated check of the source article's wording did not complete, so no result is shown.

This looks only at the wording of the original source article, not at this page's AI-written sections. A small local AI model made this estimate. It has not been checked against known human and machine texts, so treat it as provisional. It cannot show who wrote an article.

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