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-2024-7978 21 Aug 2024 128.0.6613.84 < 128.0.6613.84 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-7977 21 Aug 2024 128.0.6613.84 < 128.0.6613.84 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-7976 21 Aug 2024 128.0.6613.84 < 128.0.6613.84 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-7975 21 Aug 2024 128.0.6613.84 < 128.0.6613.84 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-7974 21 Aug 2024 128.0.6613.84 < 128.0.6613.84 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-7973 21 Aug 2024 128.0.6613.84 < 128.0.6613.84 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-7972 21 Aug 2024 128.0.6613.84 < 128.0.6613.84 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-7969 21 Aug 2024 128.0.6613.113 < 128.0.6613.113 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7968 21 Aug 2024 128.0.6613.84 < 128.0.6613.84 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-7967 21 Aug 2024 128.0.6613.84 < 128.0.6613.84 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-7966 21 Aug 2024 128.0.6613.84 < 128.0.6613.84 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-2024-7964 21 Aug 2024 128.0.6613.84 < 128.0.6613.84 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-7550 6 Aug 2024 127.0.6533.99 < 127.0.6533.99 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7536 6 Aug 2024 127.0.6533.99 < 127.0.6533.99 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7535 6 Aug 2024 127.0.6533.99 < 127.0.6533.99 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7534 6 Aug 2024 127.0.6533.99 < 127.0.6533.99 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7533 6 Aug 2024 127.0.6533.99 < 127.0.6533.99 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7532 6 Aug 2024 127.0.6533.99 < 127.0.6533.99 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-2024-7005 6 Aug 2024 127.0.6533.72 < 127.0.6533.72 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7004 6 Aug 2024 127.0.6533.72 < 127.0.6533.72 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7003 6 Aug 2024 127.0.6533.72 < 127.0.6533.72 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7001 6 Aug 2024 127.0.6533.72 < 127.0.6533.72 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7000 6 Aug 2024 127.0.6533.72 < 127.0.6533.72 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-6999 6 Aug 2024 127.0.6533.72 < 127.0.6533.72 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-6998 6 Aug 2024 127.0.6533.72 < 127.0.6533.72 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-6997 6 Aug 2024 127.0.6533.72 < 127.0.6533.72 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-6996 6 Aug 2024 127.0.6533.72 < 127.0.6533.72 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-6995 6 Aug 2024 127.0.6533.72 < 127.0.6533.72 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-6994 6 Aug 2024 127.0.6533.72 < 127.0.6533.72 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-6991 6 Aug 2024 127.0.6533.72 < 127.0.6533.72 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-6989 6 Aug 2024 127.0.6533.72 < 127.0.6533.72 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-6988 6 Aug 2024 127.0.6533.72 < 127.0.6533.72 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7256 1 Aug 2024 127.0.6533.88 < 127.0.6533.88 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7255 1 Aug 2024 127.0.6533.88 < 127.0.6533.88 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-6990 1 Aug 2024 127.0.6533.88 < 127.0.6533.88 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-3176 16 Jul 2024 117.0.5938.62 < 117.0.5938.62 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-7012 16 Jul 2024 117.0.5938.62 < 117.0.5938.62 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-7010 16 Jul 2024 117.0.5938.62 < 117.0.5938.62 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-4860 16 Jul 2024 115.0.5790.98 < 115.0.5790.98 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-2020-36765 16 Jul 2024 85.0.4183.83 < 85.0.4183.83 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-25154 16 Jul 2024 77.0.3865.75 < 77.0.3865.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-5500 16 Jul 2024 122.0.6261.57 < 122.0.6261.57 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-3175 16 Jul 2024 120.0.6099.62 < 120.0.6099.62 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-3174 16 Jul 2024 119.0.6045.105 < 119.0.6045.105 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-3173 16 Jul 2024 120.0.6099.62 < 120.0.6099.62 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-3172 16 Jul 2024 121.0.6167.85 < 121.0.6167.85 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-3171 16 Jul 2024 122.0.6261.57 < 122.0.6261.57 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-3170 16 Jul 2024 121.0.6167.85 < 121.0.6167.85 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-3169 16 Jul 2024 121.0.6167.139 < 121.0.6167.139 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-3168 16 Jul 2024 122.0.6261.57 < 122.0.6261.57 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.