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 26, 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

• Winter: Stored XSS through Brand Settings custom stylesSame generic ecosystem
• Winter: Stored XSS through Editor Settings custom stylesSame generic ecosystem
• Winter: Authenticated backend users can bypass Users controller permission checksSame generic ecosystem
• Nagios Core CSRF via cmd.cgiSame generic ecosystem
• Nagios Core / XI CSRF via cmd.cgi Double-Submit CookieSame generic ecosystem
• SENAITE.CORE: Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') and Missing Authorization in senaite.coreSame generic ecosystem