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

Publisher not identified

Google Chrome prior to 57.0.2987.98 for Mac, Windows and Linux, and 57.0.2987.108 for Android

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

Lifecycle evidence status

This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.

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-2017-5051 25 Apr 2017 Google Chrome prior to 57.0.2987.98 for Mac, Windows and Linux, and 57.0.2987.108 for Android No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-5050 25 Apr 2017 Google Chrome prior to 57.0.2987.98 for Mac, Windows and Linux, and 57.0.2987.108 for Android No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-5049 25 Apr 2017 Google Chrome prior to 57.0.2987.98 for Mac, Windows and Linux, and 57.0.2987.108 for Android No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-5048 25 Apr 2017 Google Chrome prior to 57.0.2987.98 for Mac, Windows and Linux, and 57.0.2987.108 for Android No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-5047 25 Apr 2017 Google Chrome prior to 57.0.2987.98 for Mac, Windows and Linux, and 57.0.2987.108 for Android No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-5046 24 Apr 2017 Google Chrome prior to 57.0.2987.98 for Mac, Windows and Linux, and 57.0.2987.108 for Android No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-5045 24 Apr 2017 Google Chrome prior to 57.0.2987.98 for Mac, Windows and Linux, and 57.0.2987.108 for Android No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-5044 24 Apr 2017 Google Chrome prior to 57.0.2987.98 for Mac, Windows and Linux, and 57.0.2987.108 for Android No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-5042 24 Apr 2017 Google Chrome prior to 57.0.2987.98 for Mac, Windows and Linux, and 57.0.2987.108 for Android No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-5040 24 Apr 2017 Google Chrome prior to 57.0.2987.98 for Mac, Windows and Linux, and 57.0.2987.108 for Android No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-5039 24 Apr 2017 Google Chrome prior to 57.0.2987.98 for Mac, Windows and Linux, and 57.0.2987.108 for Android No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-5037 24 Apr 2017 Google Chrome prior to 57.0.2987.98 for Mac, Windows and Linux, and 57.0.2987.108 for Android No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-5036 24 Apr 2017 Google Chrome prior to 57.0.2987.98 for Mac, Windows and Linux, and 57.0.2987.108 for Android No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-5033 24 Apr 2017 Google Chrome prior to 57.0.2987.98 for Mac, Windows and Linux, and 57.0.2987.108 for Android No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-5029 24 Apr 2017 Google Chrome prior to 57.0.2987.98 for Mac, Windows and Linux, and 57.0.2987.108 for Android 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.