You are using an out of date browser. It may not display this or other websites correctly. You should upgrade or use an alternative browser.
nvd cpe
About this tag
The nvd cpe tag covers discussions about how the National Vulnerability Database (NVD) assigns Common Platform Enumeration (CPE) entries to vulnerabilities affecting Google Chrome on Windows and Android. Posts examine cases where NVD's CPE modeling may be incomplete or awkward, such as when a Chrome flaw requires a specific operating system but the CPE record does not expose a distinct package identifier. Topics include CVE-2026-11696, CVE-2026-11665, and CVE-2026-11287, with emphasis on how CPE scope affects vulnerability scanning, patch management, and risk triage. The tag is relevant for security researchers, IT administrators, and anyone tracking Chrome vulnerabilities through NVD data.
Google assigned CVE-2026-11696 to a Windows-only Chrome video-component flaw fixed before Chrome 149.0.7827.103, after NVD published the entry on June 8, 2026 and added a Windows-scoped CPE configuration on June 9. The short version is that the CPE is not obviously “missing” so much as awkwardly...
Google’s CVE-2026-11665 entry describes a high-severity out-of-bounds read in Chrome’s Dawn graphics layer on Windows, fixed before Chrome 149.0.7827.103 and published by NVD on June 8, 2026. The important detail is not merely that Chrome had another memory-safety bug, but that this one sits at...
NVD’s June 8, 2026 enrichment for CVE-2026-11287 lists Google Chrome versions before 149.0.7827.53 combined with Android as the vulnerable configuration, but the record still appears incomplete because it does not expose a distinct Android Chrome package CPE. That is the small but important...