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-2026-13911 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13910 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13909 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13908 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13907 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13906 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13905 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13904 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13903 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13902 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13901 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13900 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13899 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13898 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13897 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13896 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13895 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13894 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13893 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13892 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13891 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13890 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13889 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13888 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13887 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13886 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13885 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 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-2026-13884 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13883 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 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-2026-13882 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13881 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13880 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13879 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13878 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13877 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 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-2026-13876 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13875 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13874 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13873 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13872 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13871 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13870 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13869 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13868 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13867 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13866 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13865 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13864 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13863 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13862 30 Jun 2026 150.0.7871.47 < 150.0.7871.47 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.