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-2022-2165 28 Jul 2022 unspecified < 103.0.5060.53 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-2164 28 Jul 2022 unspecified < 103.0.5060.53 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-2162 28 Jul 2022 unspecified < 103.0.5060.53 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-2161 28 Jul 2022 unspecified < 103.0.5060.53 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-2160 28 Jul 2022 unspecified < 103.0.5060.53 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-2158 28 Jul 2022 unspecified < 103.0.5060.53 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-2157 28 Jul 2022 unspecified < 103.0.5060.53 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-2156 28 Jul 2022 unspecified < 103.0.5060.53 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-2011 28 Jul 2022 unspecified < 102.0.5005.115 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-2010 28 Jul 2022 unspecified < 102.0.5005.115 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-2008 28 Jul 2022 unspecified < 102.0.5005.115 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-2007 28 Jul 2022 unspecified < 102.0.5005.115 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-2481 28 Jul 2022 unspecified < 103.0.5060.134 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-2480 28 Jul 2022 unspecified < 103.0.5060.134 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-2479 28 Jul 2022 unspecified < 103.0.5060.134 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-2478 28 Jul 2022 unspecified < 103.0.5060.134 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-2477 28 Jul 2022 unspecified < 103.0.5060.134 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1919 28 Jul 2022 unspecified < 101.0.4951.41 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2022-1876 27 Jul 2022 unspecified < 102.0.5005.61 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-1875 27 Jul 2022 unspecified < 102.0.5005.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1874 27 Jul 2022 unspecified < 102.0.5005.61 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-1873 27 Jul 2022 unspecified < 102.0.5005.61 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-1872 27 Jul 2022 unspecified < 102.0.5005.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1871 27 Jul 2022 unspecified < 102.0.5005.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1870 27 Jul 2022 unspecified < 102.0.5005.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1869 27 Jul 2022 unspecified < 102.0.5005.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1868 27 Jul 2022 unspecified < 102.0.5005.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1867 27 Jul 2022 unspecified < 102.0.5005.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1866 27 Jul 2022 unspecified < 102.0.5005.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1865 27 Jul 2022 unspecified < 102.0.5005.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1864 27 Jul 2022 unspecified < 102.0.5005.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1863 27 Jul 2022 unspecified < 102.0.5005.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1862 27 Jul 2022 unspecified < 102.0.5005.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1861 27 Jul 2022 unspecified < 102.0.5005.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1860 27 Jul 2022 unspecified < 102.0.5005.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1859 27 Jul 2022 unspecified < 102.0.5005.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1858 27 Jul 2022 unspecified < 102.0.5005.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1857 27 Jul 2022 unspecified < 102.0.5005.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1856 27 Jul 2022 unspecified < 102.0.5005.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1855 27 Jul 2022 unspecified < 102.0.5005.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1854 27 Jul 2022 unspecified < 102.0.5005.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1853 27 Jul 2022 unspecified < 102.0.5005.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1641 26 Jul 2022 unspecified < 101.0.4951.64 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-1640 26 Jul 2022 unspecified < 101.0.4951.64 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1639 26 Jul 2022 unspecified < 101.0.4951.64 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1638 26 Jul 2022 unspecified < 101.0.4951.64 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1637 26 Jul 2022 unspecified < 101.0.4951.64 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1636 26 Jul 2022 unspecified < 101.0.4951.64 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1635 26 Jul 2022 unspecified < 101.0.4951.64 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1634 26 Jul 2022 unspecified < 101.0.4951.64 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.