-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
495 Published CVEs do not have a datePublished value #137
Comments
Discussed at AWG meeting on Dec 3, 2025: these records will be fixed and the missing date will be added. @jayjacobs please provide a complete list of affected CVEs. This will most likely happen in Jan 2025. |
Attaching a CSV of the 495 CVE IDs. |
The cause of this issue was patched. The fix to put the datePublished field into these CVE IDs is being scheduled to be rolled out. |
@M-nj, is there any time line on when these dates might be added? |
Unofficial insight: The current plan is for January 2025. |
I seem to remember this coming up before but not sure if there was any resolution.
As of today there are 495 CVEs in a PUBLISHED state with no datePublished value in the record. The CNA is always MITRE.
Examples:
https://cveawg.mitre.org/api/cve/CVE-2022-32505
https://cveawg.mitre.org/api/cve/CVE-2024-36604
https://cveawg.mitre.org/api/cve/CVE-2024-33470
https://cveawg.mitre.org/api/cve/CVE-2023-30309
https://cveawg.mitre.org/api/cve/CVE-2024-36728
https://cveawg.mitre.org/api/cve/CVE-2024-22774
https://cveawg.mitre.org/api/cve/CVE-2024-27593
https://cveawg.mitre.org/api/cve/CVE-2024-34310
https://cveawg.mitre.org/api/cve/CVE-2023-30307
https://cveawg.mitre.org/api/cve/CVE-2024-33818
The text was updated successfully, but these errors were encountered: