CISA ADP Vulnrichment

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps Google/Chrome (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Google/Chrome.
2. 2Review the reported fix. Update Google/Chrome to 151.0.7922.173 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

1. Published upstream

   Aug 20, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Aug 21, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Aug 20, 2026

Sources and claim methodology

• Source referencechromereleases.googleblog.com
• Source referenceissues.chromium.org

Related CVEs

• llama.cpp Use-After-Free in RPC GRAPH_RECOMPUTE HandlerAlso CWE-416
• Missing privilege check in SecureContext_FreeContext in FreeRTOS-KernelAlso CWE-416
• Authenticated Remote Code Execution via Stack-Based Buffer Overflow in Firmware Update HandlingSame generic ecosystem
• Unauthenticated Denial of Service via Null Pointer Dereference in HTTP Request ParsingSame generic ecosystem
• Unauthenticated Denial of Service via Composed HTTP Parsing and Stack-Based Out-of-Bounds Write Vulnerability in TL-MR6400 Web Management InterfaceSame generic ecosystem
• OpenViking < 0.3.4 SSRF via /api/v1/resourcesSame generic ecosystem