Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY5310 SECURITY RECORDS

Google

Chrome

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

Official registry publication history is available at chrome, but registry activity is not a publisher support boundary.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-84329 1 Sep 2026 152.0.7977.75 < 152.0.7977.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-84327 1 Sep 2026 152.0.7977.75 < 152.0.7977.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-84335 1 Sep 2026 152.0.7977.75 < 152.0.7977.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-84348 1 Sep 2026 152.0.7977.75 < 152.0.7977.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-84334 1 Sep 2026 152.0.7977.75 < 152.0.7977.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-84330 1 Sep 2026 152.0.7977.75 < 152.0.7977.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-84332 1 Sep 2026 Chrome: 152.0.7977.75 < 152.0.7977.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-84358 1 Sep 2026 152.0.7977.75 < 152.0.7977.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-84355 1 Sep 2026 152.0.7977.75 < 152.0.7977.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-84323 1 Sep 2026 152.0.7977.75 < 152.0.7977.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-84347 1 Sep 2026 152.0.7977.75 < 152.0.7977.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-84328 1 Sep 2026 152.0.7977.75 < 152.0.7977.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-84325 1 Sep 2026 Chrome: 152.0.7977.75 < 152.0.7977.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-84351 1 Sep 2026 152.0.7977.75 < 152.0.7977.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-84333 1 Sep 2026 152.0.7977.75 < 152.0.7977.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-84326 1 Sep 2026 152.0.7977.75 < 152.0.7977.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-84349 1 Sep 2026 152.0.7977.75 < 152.0.7977.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-84324 1 Sep 2026 152.0.7977.75 < 152.0.7977.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-84357 1 Sep 2026 Chrome: 152.0.7977.75 < 152.0.7977.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-84359 1 Sep 2026 152.0.7977.75 < 152.0.7977.75 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Update reference ↗
CVE-2026-84354 1 Sep 2026 152.0.7977.75 < 152.0.7977.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-84352 1 Sep 2026 152.0.7977.75 < 152.0.7977.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-84353 1 Sep 2026 152.0.7977.75 < 152.0.7977.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-82072 27 Aug 2026 151.0.7922.72 < 151.0.7922.72 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-78964 25 Aug 2026 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-78914 25 Aug 2026 152.0.7977.65 < 152.0.7977.65 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Update reference ↗
CVE-2026-79254 25 Aug 2026 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-79260 25 Aug 2026 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-79253 25 Aug 2026 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-78915 25 Aug 2026 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-79126 25 Aug 2026 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-78957 25 Aug 2026 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-78981 25 Aug 2026 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-79152 25 Aug 2026 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-79179 25 Aug 2026 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-79133 25 Aug 2026 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-79021 25 Aug 2026 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-79225 25 Aug 2026 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-79105 25 Aug 2026 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-79017 25 Aug 2026 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-79207 25 Aug 2026 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-79125 25 Aug 2026 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-79148 25 Aug 2026 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-79197 25 Aug 2026 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-79045 25 Aug 2026 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-79223 25 Aug 2026 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-79246 25 Aug 2026 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-79112 25 Aug 2026 152.0.7977.65 < 152.0.7977.65 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Update reference ↗
CVE-2026-79244 25 Aug 2026 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-78947 25 Aug 2026 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.