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-2019-13765 3 Jan 2020 unspecified < 78.0.3904.70 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-5815 11 Dec 2019 unspecified < 74.0.3729.108 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13764 10 Dec 2019 unspecified < 79.0.3945.79 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-2019-13763 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13762 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13761 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13759 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13758 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13757 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13756 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13755 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13754 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13753 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13752 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13751 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13750 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13749 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13748 10 Dec 2019 unspecified < 79.0.3945.79 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-2019-13747 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13746 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13745 10 Dec 2019 unspecified < 79.0.3945.79 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-2019-13744 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13743 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13742 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13741 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13740 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13739 10 Dec 2019 unspecified < 79.0.3945.79 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-2019-13738 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13737 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13736 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13735 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13734 10 Dec 2019 unspecified < 79.0.3945.79 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-2019-13732 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13730 10 Dec 2019 unspecified < 79.0.3945.79 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-2019-13729 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13728 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13727 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13726 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13725 10 Dec 2019 unspecified < 79.0.3945.79 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-5843 10 Dec 2019 unspecified < 74.0.3729.108 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-5841 10 Dec 2019 unspecified < 75.0.3770.80 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-13672 10 Dec 2019 unspecified < 77.0.3865.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-5826 25 Nov 2019 unspecified < 73.0.3683.86 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-5881 25 Nov 2019 unspecified < 77.0.3865.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-5880 25 Nov 2019 unspecified < 77.0.3865.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-5879 25 Nov 2019 unspecified < 77.0.3865.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-5878 25 Nov 2019 unspecified < 77.0.3865.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-5877 25 Nov 2019 unspecified < 77.0.3865.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-5876 25 Nov 2019 unspecified < 77.0.3865.75 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-5875 25 Nov 2019 unspecified < 77.0.3865.75 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.