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

Evidence timeline and material changes

1. Published upstream

   Aug 27, 2026

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

2. Source modified

   Aug 28, 2026

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

3. First seen by HOL

   Aug 27, 2026

Sources and claim methodology

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

Related CVEs

• Gimp: heap out-of-bounds reads in iff/ilbm loader from ham row size mismatch and nplanes=0Also CWE-125
• Gimp: heap out-of-bounds read in ico loader via unvalidated used_clrs palette countAlso CWE-125
• Gimp: heap out-of-bounds read in pvr vq (compressed) decoder due to missing bounds checkAlso CWE-125
• Pega Platform versions 7.1.0 through 25.1.2 are affected by an improper validation of inputs that are used for loop conditions, potentially leading to a denial of service or other consequences because of excessive looping.Same generic ecosystem
• morgan vulnerable to Log Forging via unescaped Unicode line separatorsSame generic ecosystem
• Hardcoded Credentials Vulnerability in CP Plus CP-XR-DE21-S RouterSame generic ecosystem