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.169 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

1. Published upstream

   Aug 18, 2026

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

2. Source modified

   Aug 19, 2026

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

3. First seen by HOL

   Aug 18, 2026

Sources and claim methodology

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

Related CVEs

• Use-after-free in kqueue copy-on-forkAlso CWE-416
• User Verification <= 2.0.47 - Unauthenticated Arbitrary Account Lockout via IDORSame generic ecosystem
• Easy Media Replace <= 0.2.0 - Author+ Stored XSS via Attachment TitleSame generic ecosystem
• EWWW Image Optimizer <= 8.7.3 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'data-script' Lazy Load Attribute in Post ContentSame generic ecosystem
• WP Statistics <= 14.16.8 - Unauthenticated Stored Cross-Site Scripting via 'utm_campaign' ParameterSame generic ecosystem
• YayCurrency < 3.3.5 - Unauthenticated Order and Vendor Financial Data Disclosure via Dokan IntegrationSame generic ecosystem