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-79185 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-79182 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-79004 25 Aug 2026 Chrome: 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-78963 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-78984 25 Aug 2026 Chrome: 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-78960 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-79075 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-79034 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-79221 25 Aug 2026 Chrome: 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-79139 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-79033 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-79203 25 Aug 2026 Chrome: 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-79227 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-79097 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-78901 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-78962 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-79252 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-79211 25 Aug 2026 Chrome: 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-79258 25 Aug 2026 Chrome: 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-78913 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-79265 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-79091 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-79249 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-78951 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-79220 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-79003 25 Aug 2026 Chrome: 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-79064 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-79134 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-79085 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-79269 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-79068 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-79230 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-79154 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-79103 25 Aug 2026 Chrome: 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-78978 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-79245 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-79059 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-79178 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-78944 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-79083 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-78983 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-79234 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-78959 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-78903 25 Aug 2026 Chrome: 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-79205 25 Aug 2026 Chrome: 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-79070 25 Aug 2026 Chrome: 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-78892 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-79283 25 Aug 2026 Chrome: 152.0.7977.65 < 152.0.7977.65 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-79291 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-78949 25 Aug 2026 Chrome: 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.