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

Evidence timeline and material changes

1. Published upstream

   Sep 9, 2026

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

2. Source modified

   Sep 10, 2026

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

3. First seen by HOL

   Sep 9, 2026

Sources and claim methodology

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

Related CVEs

• Open WebUI: Users denied by the OAuth domain allowlist or role policy can still sign in via token exchangeAlso CWE-863
• Open WebUI: Users denied by the OAuth role policy can still sign in via token exchangeAlso CWE-863
• Traefik HTTP/3 Backend NTLM Connection ReuseAlso CWE-863
• Traefik: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') and Incorrect AuthorizationAlso CWE-863
• knowns through 0.33.0 Authorization Bypass via project.set Bootstrap ExemptionAlso CWE-863
• Type confusion in Zephyr HL78xx GNSS NMEA driver causes wild-pointer write from GNSS inputSame generic ecosystem