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-2020-6521 22 Jul 2020 unspecified < 84.0.4147.89 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6520 22 Jul 2020 unspecified < 84.0.4147.89 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6519 22 Jul 2020 unspecified < 84.0.4147.89 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6518 22 Jul 2020 unspecified < 84.0.4147.89 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6517 22 Jul 2020 unspecified < 84.0.4147.89 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6516 22 Jul 2020 unspecified < 84.0.4147.89 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6515 22 Jul 2020 unspecified < 84.0.4147.89 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6514 22 Jul 2020 unspecified < 84.0.4147.89 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6513 22 Jul 2020 unspecified < 84.0.4147.89 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6512 22 Jul 2020 unspecified < 84.0.4147.89 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6511 22 Jul 2020 unspecified < 84.0.4147.89 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6510 22 Jul 2020 unspecified < 84.0.4147.89 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6509 22 Jul 2020 unspecified < 83.0.4103.116 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6507 22 Jul 2020 unspecified < 83.0.4103.106 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-2020-6506 22 Jul 2020 unspecified < 83.0.4103.106 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6505 22 Jul 2020 unspecified < 83.0.4103.106 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6504 3 Jun 2020 unspecified < 74.0.3729.108 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6503 3 Jun 2020 unspecified < 74.0.3729.108 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-2020-6502 3 Jun 2020 unspecified < 80.0.3987.87 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6501 3 Jun 2020 unspecified < 80.0.3987.87 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6500 3 Jun 2020 unspecified < 80.0.3987.87 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6499 3 Jun 2020 unspecified < 80.0.3987.87 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6498 3 Jun 2020 unspecified < 83.0.4103.88 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6497 3 Jun 2020 unspecified < 83.0.4103.88 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6496 3 Jun 2020 unspecified < 83.0.4103.97 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6495 3 Jun 2020 unspecified < 83.0.4103.97 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6494 3 Jun 2020 unspecified < 83.0.4103.97 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6493 3 Jun 2020 unspecified < 83.0.4103.97 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6453 3 Jun 2020 unspecified < 80.0.3987.162 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6419 3 Jun 2020 unspecified < 81.0.4044.92 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-2011-2863 3 Jun 2020 unspecified < 14.0.0.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2011-1805 3 Jun 2020 unspecified < 11.0.0.0 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-2020-6491 21 May 2020 unspecified < 83.0.4103.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6490 21 May 2020 unspecified < 83.0.4103.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6489 21 May 2020 unspecified < 83.0.4103.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6488 21 May 2020 unspecified < 83.0.4103.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6487 21 May 2020 unspecified < 83.0.4103.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6486 21 May 2020 unspecified < 83.0.4103.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6485 21 May 2020 unspecified < 83.0.4103.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6484 21 May 2020 unspecified < 83.0.4103.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6483 21 May 2020 unspecified < 83.0.4103.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6482 21 May 2020 unspecified < 83.0.4103.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6481 21 May 2020 unspecified < 83.0.4103.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6480 21 May 2020 unspecified < 83.0.4103.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6479 21 May 2020 unspecified < 83.0.4103.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6478 21 May 2020 unspecified < 83.0.4103.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6477 21 May 2020 unspecified < 83.0.4103.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6476 21 May 2020 unspecified < 83.0.4103.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6475 21 May 2020 unspecified < 83.0.4103.61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6474 21 May 2020 unspecified < 83.0.4103.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 ↗

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.