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

Evidence timeline and material changes

1. Published upstream

   Aug 25, 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 25, 2026

Sources and claim methodology

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

Related CVEs

• Klever-Go: Marketplace settlement mints KLV when referral % + royalty % exceed the bid (negative seller share silently skipped)Also CWE-367
• Klever-Go: Integer overflow in split-royalty validation enables unbounded minting of KLV (native token)Same generic ecosystem
• Vikunja: Project duplication bypasses write-permission check on the target parent projectSame generic ecosystem
• dd-trace-rs: Unbounded W3C tracestate parsing may lead to DoSSame generic ecosystem
• Vikunja incomplete fix for CVE-2026-35595: Write-only user can detach shared project from parent hierarchy via parent_project_id=0Same generic ecosystem
• Vikunja: Improper Authorization and Authorization Bypass Through User-Controlled Key in code.vikunja.io/apiSame generic ecosystem