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-9965 15 Oct 2024 130.0.6723.58 < 130.0.6723.58 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-9964 15 Oct 2024 130.0.6723.58 < 130.0.6723.58 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-9963 15 Oct 2024 130.0.6723.58 < 130.0.6723.58 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-9962 15 Oct 2024 130.0.6723.58 < 130.0.6723.58 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-9961 15 Oct 2024 130.0.6723.58 < 130.0.6723.58 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-9960 15 Oct 2024 130.0.6723.58 < 130.0.6723.58 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-9959 15 Oct 2024 130.0.6723.58 < 130.0.6723.58 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-9958 15 Oct 2024 130.0.6723.58 < 130.0.6723.58 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-9957 15 Oct 2024 130.0.6723.58 < 130.0.6723.58 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-9956 15 Oct 2024 130.0.6723.58 < 130.0.6723.58 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-9955 15 Oct 2024 130.0.6723.58 < 130.0.6723.58 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-9954 15 Oct 2024 130.0.6723.58 < 130.0.6723.58 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-9859 11 Oct 2024 126.0.6478.126 < 126.0.6478.126 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-9603 8 Oct 2024 129.0.6668.100 < 129.0.6668.100 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-9602 8 Oct 2024 129.0.6668.100 < 129.0.6668.100 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-9123 24 Sep 2024 129.0.6668.70 < 129.0.6668.70 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-9122 24 Sep 2024 129.0.6668.70 < 129.0.6668.70 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-9121 24 Sep 2024 129.0.6668.70 < 129.0.6668.70 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-9120 24 Sep 2024 129.0.6668.70 < 129.0.6668.70 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7024 23 Sep 2024 126.0.6478.54 < 126.0.6478.54 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7023 23 Sep 2024 128.0.6537.0 < 128.0.6537.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2018-20072 23 Sep 2024 73.0.3683.75 < 73.0.3683.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-38023 23 Sep 2024 92.0.4515.107 < 92.0.4515.107 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-7282 23 Sep 2024 113.0.5672.63 < 113.0.5672.63 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-7281 23 Sep 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-7022 23 Sep 2024 123.0.6312.58 < 123.0.6312.58 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7020 23 Sep 2024 124.0.6367.60 < 124.0.6367.60 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7019 23 Sep 2024 124.0.6367.60 < 124.0.6367.60 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7018 23 Sep 2024 124.0.6367.78 < 124.0.6367.78 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8909 17 Sep 2024 129.0.6668.58 < 129.0.6668.58 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8908 17 Sep 2024 129.0.6668.58 < 129.0.6668.58 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8907 17 Sep 2024 129.0.6668.58 < 129.0.6668.58 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8906 17 Sep 2024 129.0.6668.58 < 129.0.6668.58 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8905 17 Sep 2024 129.0.6668.58 < 129.0.6668.58 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8904 17 Sep 2024 129.0.6668.58 < 129.0.6668.58 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8639 11 Sep 2024 128.0.6613.137 < 128.0.6613.137 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8638 11 Sep 2024 128.0.6613.137 < 128.0.6613.137 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8637 11 Sep 2024 128.0.6613.137 < 128.0.6613.137 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8636 11 Sep 2024 128.0.6613.137 < 128.0.6613.137 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-7970 3 Sep 2024 128.0.6613.119 < 128.0.6613.119 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8362 3 Sep 2024 128.0.6613.119 < 128.0.6613.119 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8198 28 Aug 2024 128.0.6613.113 < 128.0.6613.113 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-8194 28 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-8193 28 Aug 2024 128.0.6613.113 < 128.0.6613.113 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-8035 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-8034 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-8033 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-7981 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-7980 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-7979 21 Aug 2024 128.0.6613.84 < 128.0.6613.84 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗

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.