|
1 | 1 | { |
2 | 2 | "currentNews": [ |
| 3 | + { |
| 4 | + "id": 628, |
| 5 | + "displayOnHomepageOrder": 1, |
| 6 | + "newsType": "blog", |
| 7 | + "title": "NOTICE: Date/Time Normalization Maintenance of Historical CVE Records to Occur February 16–25, 2026", |
| 8 | + "urlKeywords": "Historic CVE Record Date Time Maintenance February", |
| 9 | + "date": "2026-02-10", |
| 10 | + "author": { |
| 11 | + "name": "CVE Program", |
| 12 | + "organization": { |
| 13 | + "name": "CVE Program", |
| 14 | + "url": "" |
| 15 | + }, |
| 16 | + "title": "", |
| 17 | + "bio": "" |
| 18 | + }, |
| 19 | + "description": [ |
| 20 | + { |
| 21 | + "contentnewsType": "paragraph", |
| 22 | + "content": "The <a href='/'>CVE™ Program</a> will normalize the formatting of date/time fields across historical <a href='/ResourcesSupport/Glossary?activeTerm=glossaryRecord'>CVE Records</a> from February 16, 2026, through February 25, 2026. As <a href='/Media/News/item/blog/2026/01/06/Historic-CVE-Record-Date-Time-Fields-Normalized'>initially announced on January 6, 2026</a>, this maintenance will update older CVE Records so their date/time values use the same standardized ISO 8601 UTC format already in place for records published or updated since February 2025: <ul style=list-style-type:none;><li><strong>yyyy-MM-ddTHH:mm:ss.sssZ (ISO-8601, UTC)</strong></li></ul>For example: <strong>2025-07-11T19:32:03.983Z</strong>" |
| 23 | + }, |
| 24 | + { |
| 25 | + "contentnewsType": "paragraph", |
| 26 | + "content": "<h3>Maintenance Window and Dates</h3>" |
| 27 | + }, |
| 28 | + { |
| 29 | + "contentnewsType": "paragraph", |
| 30 | + "content": "The normalization activity will run in defined daily windows and will proceed in stages based on the publication year of the CVE Records in the following dates and year ranges:" |
| 31 | + }, |
| 32 | + { |
| 33 | + "contentnewsType": "paragraph", |
| 34 | + "content": "<ul><li>Monday, February 16 – CVE Records published from 1999–2007</li><li>Tuesday, February 17 – CVE Records published from 2008–2012</li><li>Wednesday, February 18 – CVE Records published from 2013–2015</li><li>Thursday, February 19 – CVE Records published from 2016–2017</li><li>Friday, February 20 – CVE Records published from 2018–2019 (Part 1)</li><li>Monday, February 23 – CVE Records published from 2019 (Part 2)–2020</li><li>Tuesday, February 24 – CVE Records published from 2021–2022 (Part 1)</li><li>Wednesday, February 25 – CVE Records published from 2022 (Part 2)–2026</li></ul>" |
| 35 | + }, |
| 36 | + { |
| 37 | + "contentnewsType": "paragraph", |
| 38 | + "content": "Each day, the <strong>maintenance effort will begin at 9:30 AM EST and end at 4:30 PM EST</strong>. During this time, the system will be fully operational and will accept (and publish) new CVE Records as normal." |
| 39 | + }, |
| 40 | + { |
| 41 | + "contentnewsType": "paragraph", |
| 42 | + "content": "View the <a target='_blank' href='https://github.com/CVEProject/cvelistV5/blob/main/README.md'>CVE List Repository README</a> for more detailed information." |
| 43 | + }, |
| 44 | + { |
| 45 | + "contentnewsType": "paragraph", |
| 46 | + "content": "<h3>What Is Changing – and What Is Not</h3>" |
| 47 | + }, |
| 48 | + { |
| 49 | + "contentnewsType": "paragraph", |
| 50 | + "content": "As noted in the <a href='/Media/News/item/blog/2026/01/06/Historic-CVE-Record-Date-Time-Fields-Normalized'>January 6, 2026, blog post</a>, this maintenance affects only the formatting of specific date/time string fields (for example, datePublished, dateUpdated, dateReserved, dateRejected, datePublic, dateAssigned, and time values under timeline). The semantic meaning of the dates/times remains the same, and no other parts of the CVE Records will be changed." |
| 51 | + }, |
| 52 | + { |
| 53 | + "contentnewsType": "paragraph", |
| 54 | + "content": "<h3>Operational Updates During the Window</h3>" |
| 55 | + }, |
| 56 | + { |
| 57 | + "contentnewsType": "paragraph", |
| 58 | + "content": "In total, this process will update approximately 200,000 historical CVE Records (between 25,000 and 30,000 records each day). <strong>Some automated systems may interpret these records as “modified” during the maintenance windows and trigger reprocessing, alerts, or customer notifications.</strong>" |
| 59 | + }, |
| 60 | + { |
| 61 | + "contentnewsType": "paragraph", |
| 62 | + "content": "To help the community track progress and plan accordingly, the CVE Program will post on social media at the start and end of each maintenance window every day from February 16 through 20, and February 23 through 25." |
| 63 | + }, |
| 64 | + { |
| 65 | + "contentnewsType": "paragraph", |
| 66 | + "content": "<h3>Questions or Feedback</h3>" |
| 67 | + }, |
| 68 | + { |
| 69 | + "contentnewsType": "paragraph", |
| 70 | + "content": "We appreciate the community’s support as we continue improving the consistency and quality of CVE Records for all users." |
| 71 | + }, |
| 72 | + { |
| 73 | + "contentnewsType": "paragraph", |
| 74 | + "content": "If you have questions or concerns about this maintenance or its potential impact on your systems, please leave a comment on the <a target='_blank' href='https://medium.com/@cve_program'>CVE Blog on Medium</a> or use the <a target='_blank' href='https://cveform.mitre.org/'>CVE Request Web Form</a> and select “Other” from the dropdown menu." |
| 75 | + } |
| 76 | + ] |
| 77 | + }, |
| 78 | + { |
| 79 | + "id": 627, |
| 80 | + "newsType": "news", |
| 81 | + "title": "Project Black Added as CVE Numbering Authority (CNA)", |
| 82 | + "urlKeywords": "Project Black Added as CNA", |
| 83 | + "date": "2026-02-10", |
| 84 | + "description": [ |
| 85 | + { |
| 86 | + "contentnewsType": "paragraph", |
| 87 | + "content": "<a href='/PartnerInformation/ListofPartners/partner/PRJBLK'>Project Black</a> is now a <a href='/ResourcesSupport/Glossary?activeTerm=glossaryCNA'>CVE Numbering Authority (CNA)</a> for vulnerabilities discovered by Project Black that are not within another CNA’s scope." |
| 88 | + }, |
| 89 | + { |
| 90 | + "contentnewsType": "paragraph", |
| 91 | + "content": "To date, <a href='/PartnerInformation/ListofPartners'>492 CNAs</a> (489 CNAs and 3 CNA-LRs) from <a href='/ProgramOrganization/CNAs'>41 countries</a> and 1 no country affiliation have partnered with the CVE Program. CNAs are organizations from around the world that are authorized to assign <a href='/ResourcesSupport/Glossary?activeTerm=glossaryCVEID'>CVE Identifiers (CVE IDs)</a> and publish <a href='/ResourcesSupport/Glossary?activeTerm=glossaryRecord'>CVE Records</a> for vulnerabilities affecting products within their distinct, agreed-upon scope, for inclusion in first-time public announcements of new vulnerabilities. Project Black is the 11th CNA from Australia." |
| 92 | + }, |
| 93 | + { |
| 94 | + "contentnewsType": "paragraph", |
| 95 | + "content": "Project Black’s Root is the <a href='/PartnerInformation/ListofPartners/partner/mitre'>MITRE TL-Root</a>." |
| 96 | + } |
| 97 | + ] |
| 98 | + }, |
| 99 | + { |
| 100 | + "id": 626, |
| 101 | + "newsType": "news", |
| 102 | + "title": "Minutes from CVE Board Teleconference Meeting on January 7 Now Available", |
| 103 | + "urlKeywords": "CVE Board Minutes from January 7", |
| 104 | + "date": "2026-02-10", |
| 105 | + "description": [ |
| 106 | + { |
| 107 | + "contentnewsType": "paragraph", |
| 108 | + "content": "The <a href='/ProgramOrganization/Board'>CVE Board</a> held a teleconference meeting on January 7, 2026. Read the <a href='https://www.mail-archive.com/cve-editorial-board-list@mitre.org/msg00310.html' target='_blank'>meeting minutes summary</a>." |
| 109 | + }, |
| 110 | + { |
| 111 | + "contentnewsType": "paragraph", |
| 112 | + "content": "The CVE Board is the organization responsible for the strategic direction, governance, operational structure, policies, and rules of the CVE Program. The Board includes members from numerous cybersecurity-related organizations including commercial security tool vendors, academia, research institutions, government departments and agencies, and other prominent security experts, as well as end-users of vulnerability information." |
| 113 | + } |
| 114 | + ] |
| 115 | + }, |
3 | 116 | { |
4 | 117 | "id": 625, |
5 | 118 | "newsType": "news", |
|
206 | 319 | }, |
207 | 320 | { |
208 | 321 | "id": 616, |
209 | | - "displayOnHomepageOrder": 1, |
210 | 322 | "newsType": "blog", |
211 | 323 | "title": "CVE Program to Normalize Formatting of Date/Time Fields Across Historical CVE Records Beginning in Mid-February 2026", |
212 | 324 | "urlKeywords": "Historic CVE Record Date Time Fields Normalized", |
|
0 commit comments