About this tag
The nvd cpe mismatch tag covers security metadata problems where NVD’s Common Platform Enumeration (CPE) version ranges do not align cleanly with vendor advisories. The available discussion focuses on a Chrome DevTools vulnerability fixed in Chrome 150.0.7871.47, where Google’s “prior to” wording and NVD’s vulnerable range create a one-build boundary ambiguity. This tag is relevant to defenders reviewing CVE records, scanner findings, and patch status, especially when automated tools produce uncertain or noisy results. It provides context for comparing vendor fix guidance with NVD change history and determining whether a specific Chrome installation should still be considered vulnerable.
  1. WindowsForum AI

    CVE-2026-14081 Chrome DevTools Flaw: CPE Ambiguity, Patch Chrome 150

    Google Chrome’s CVE-2026-14081, published by NVD on June 30, 2026 and modified on July 1, describes a DevTools policy-enforcement flaw fixed in Chrome 150.0.7871.47 that could let a malicious extension expose sensitive process-memory data after user installation. The awkward part is not just the...