|
1 | 1 | { |
2 | 2 | "currentNews": [ |
| 3 | + { |
| 4 | + "id": 631, |
| 5 | + "newsType": "news", |
| 6 | + "title": "Vestel Added as CVE Numbering Authority (CNA)", |
| 7 | + "urlKeywords": "Vestel Added as CNA", |
| 8 | + "date": "2026-02-17", |
| 9 | + "description": [ |
| 10 | + { |
| 11 | + "contentnewsType": "paragraph", |
| 12 | + "content": "<a href='/PartnerInformation/ListofPartners/partner/Vestel'>Vestel Electronics Industry & Trade Co.</a> is now a <a href='/ResourcesSupport/Glossary?activeTerm=glossaryCNA'>CVE Numbering Authority (CNA)</a> for Vestel-owned brands and products only." |
| 13 | + }, |
| 14 | + { |
| 15 | + "contentnewsType": "paragraph", |
| 16 | + "content": "To date, <a href='/PartnerInformation/ListofPartners'>494 CNAs</a> (491 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. Vestel is the 4th CNA from Türkiye." |
| 17 | + }, |
| 18 | + { |
| 19 | + "contentnewsType": "paragraph", |
| 20 | + "content": "Vestel’s Root is the <a href='/PartnerInformation/ListofPartners/partner/mitre'>MITRE TL-Root</a>." |
| 21 | + } |
| 22 | + ] |
| 23 | + }, |
| 24 | + { |
| 25 | + "id": 630, |
| 26 | + "newsType": "news", |
| 27 | + "title": "DTEX Added as CVE Numbering Authority (CNA)", |
| 28 | + "urlKeywords": "DTEX Added as CNA", |
| 29 | + "date": "2026-02-17", |
| 30 | + "description": [ |
| 31 | + { |
| 32 | + "contentnewsType": "paragraph", |
| 33 | + "content": "<a href='/PartnerInformation/ListofPartners/partner/DTEX'>DTEX Systems, Inc.</a> is now a <a href='/ResourcesSupport/Glossary?activeTerm=glossaryCNA'>CVE Numbering Authority (CNA)</a> for all DTEX products, including DTEX Forwarder for Mac, DTEX Forwarder for Linux, DTEX Forwarder for Windows, and DTEX platform including DTEX Analytics Server." |
| 34 | + }, |
| 35 | + { |
| 36 | + "contentnewsType": "paragraph", |
| 37 | + "content": "To date, <a href='/PartnerInformation/ListofPartners'>493 CNAs</a> (490 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. DTEX is the 265th CNA from USA." |
| 38 | + }, |
| 39 | + { |
| 40 | + "contentnewsType": "paragraph", |
| 41 | + "content": "DTEX’s Root is the <a href='/PartnerInformation/ListofPartners/partner/mitre'>MITRE TL-Root</a>." |
| 42 | + } |
| 43 | + ] |
| 44 | + }, |
| 45 | + { |
| 46 | + "id": 629, |
| 47 | + "newsType": "news", |
| 48 | + "title": "MegaZone Reelected as CNA Liaison Board Member", |
| 49 | + "urlKeywords": "MegaZone Reelected CNA Liaison Board Member", |
| 50 | + "date": "2026-02-17", |
| 51 | + "description": [ |
| 52 | + { |
| 53 | + "contentnewsType": "paragraph", |
| 54 | + "content": "The <a href='/'>CVE Program</a> is pleased to announce that MegaZone of <a href='https://www.f5.com' target='_blank'>F5, Inc.</a>, received the majority of votes from CNAs and was reelected as the <a href='/ProgramOrganization/CNAs'>CVE Numbering Authority (CNA)</a> Liaison to the <a href='/ProgramOrganization/Board'>CVE Board</a> for another one-year term." |
| 55 | + }, |
| 56 | + { |
| 57 | + "contentnewsType": "paragraph", |
| 58 | + "content": "Per the <a href='/Resources/Roles/Board/General/Board-Charter.pdf' target='_blank'>CVE Board Charter</a>, “Section 1.3.2 CNA Liaison – A single seat on the Board is reserved for a CNA Liaison who represents the CNA community, and ensures CNAs are updated with various status and activity-related information. The liaison is a voting member of the Board, with a one-year term, and can serve more than one consecutive term if the CNA community desires. This position is a two-way conduit for CNAs to bring things to and from the Board in a more official and structured way.”" |
| 59 | + }, |
| 60 | + { |
| 61 | + "contentnewsType": "paragraph", |
| 62 | + "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." |
| 63 | + } |
| 64 | + ] |
| 65 | + }, |
3 | 66 | { |
4 | 67 | "id": 628, |
5 | 68 | "displayOnHomepageOrder": 1, |
6 | 69 | "newsType": "blog", |
7 | | - "title": "NOTICE: Date/Time Normalization Maintenance of Historical CVE Records to Occur February 16–25, 2026", |
| 70 | + "title": "NOTICE: Date/Time Normalization Maintenance of Historical CVE Records to Occur February 16–26 (UPDATED: February 17, 2026)", |
8 | 71 | "urlKeywords": "Historic CVE Record Date Time Maintenance February", |
9 | 72 | "date": "2026-02-10", |
10 | 73 | "author": { |
|
19 | 82 | "description": [ |
20 | 83 | { |
21 | 84 | "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>" |
| 85 | + "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 26, 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 ><br/<br/><br/><i>NOTE: This article was revised on February 17, 2026, to add an additional day of processing to this CVE List maintenance schedule to address potential inconsistencies identified during the first day, February 16, 2026.</i>" |
23 | 86 | }, |
24 | 87 | { |
25 | 88 | "contentnewsType": "paragraph", |
26 | 89 | "content": "<h3>Maintenance Window and Dates</h3>" |
27 | 90 | }, |
28 | 91 | { |
29 | 92 | "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:" |
| 93 | + "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." |
| 94 | + }, |
| 95 | + { |
| 96 | + "contentnewsType": "paragraph", |
| 97 | + "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><li>Thursday, February 26 – Quality Control Review/Modification 1999-2007<sup>*</sup></li></ul>" |
31 | 98 | }, |
32 | 99 | { |
33 | 100 | "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>" |
| 101 | + "content": "<i>* An additional day of processing has been added to address potential inconsistencies identified during the first day (i.e., February 16, 2026) of the maintenance activity.</i>" |
35 | 102 | }, |
36 | 103 | { |
37 | 104 | "contentnewsType": "paragraph", |
|
59 | 126 | }, |
60 | 127 | { |
61 | 128 | "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." |
| 129 | + "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 26." |
63 | 130 | }, |
64 | 131 | { |
65 | 132 | "contentnewsType": "paragraph", |
|
0 commit comments