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-3541 4 Mar 2026 145.0.7632.159 < 145.0.7632.159 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-3540 4 Mar 2026 145.0.7632.159 < 145.0.7632.159 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-3538 4 Mar 2026 145.0.7632.159 < 145.0.7632.159 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-3537 4 Mar 2026 145.0.7632.159 < 145.0.7632.159 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-3536 4 Mar 2026 145.0.7632.159 < 145.0.7632.159 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-3063 23 Feb 2026 145.0.7632.116 < 145.0.7632.116 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-3062 23 Feb 2026 145.0.7632.116 < 145.0.7632.116 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-3061 23 Feb 2026 145.0.7632.116 < 145.0.7632.116 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-2650 18 Feb 2026 145.0.7632.109 < 145.0.7632.109 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-2649 18 Feb 2026 145.0.7632.109 < 145.0.7632.109 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-2648 18 Feb 2026 145.0.7632.109 < 145.0.7632.109 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-2323 11 Feb 2026 145.0.7632.45 < 145.0.7632.45 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-2322 11 Feb 2026 145.0.7632.45 < 145.0.7632.45 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-2321 11 Feb 2026 145.0.7632.45 < 145.0.7632.45 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-2320 11 Feb 2026 145.0.7632.45 < 145.0.7632.45 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-2319 11 Feb 2026 145.0.7632.45 < 145.0.7632.45 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-2318 11 Feb 2026 145.0.7632.45 < 145.0.7632.45 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-2317 11 Feb 2026 145.0.7632.45 < 145.0.7632.45 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-2316 11 Feb 2026 145.0.7632.45 < 145.0.7632.45 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-2315 11 Feb 2026 145.0.7632.45 < 145.0.7632.45 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-2314 11 Feb 2026 145.0.7632.45 < 145.0.7632.45 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-2313 11 Feb 2026 145.0.7632.45 < 145.0.7632.45 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-1862 3 Feb 2026 144.0.7559.132 < 144.0.7559.132 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-1861 3 Feb 2026 144.0.7559.132 < 144.0.7559.132 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-1504 27 Jan 2026 144.0.7559.110 < 144.0.7559.110 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0908 20 Jan 2026 144.0.7559.59 < 144.0.7559.59 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-0907 20 Jan 2026 144.0.7559.59 < 144.0.7559.59 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-0906 20 Jan 2026 144.0.7559.59 < 144.0.7559.59 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-0905 20 Jan 2026 144.0.7559.59 < 144.0.7559.59 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-0904 20 Jan 2026 144.0.7559.59 < 144.0.7559.59 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-0903 20 Jan 2026 144.0.7559.59 < 144.0.7559.59 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-0902 20 Jan 2026 144.0.7559.59 < 144.0.7559.59 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-0901 20 Jan 2026 144.0.7559.59 < 144.0.7559.59 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-0900 20 Jan 2026 144.0.7559.59 < 144.0.7559.59 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-0899 20 Jan 2026 144.0.7559.59 < 144.0.7559.59 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-0628 6 Jan 2026 143.0.7499.192 < 143.0.7499.192 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-14766 16 Dec 2025 Chrome: 143.0.7499.147 < 143.0.7499.147 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-14765 16 Dec 2025 Chrome: 143.0.7499.147 < 143.0.7499.147 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-14373 12 Dec 2025 Chrome: 143.0.7499.110 < 143.0.7499.110 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-14372 12 Dec 2025 Chrome: 143.0.7499.110 < 143.0.7499.110 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-13992 3 Dec 2025 Chrome: 139.0.7258.66 < 139.0.7258.66 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-13633 2 Dec 2025 Chrome: 143.0.7499.41 < 143.0.7499.41 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-13721 2 Dec 2025 Chrome: 143.0.7499.41 < 143.0.7499.41 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-13720 2 Dec 2025 Chrome: 143.0.7499.41 < 143.0.7499.41 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-13640 2 Dec 2025 143.0.7499.41 < 143.0.7499.41 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-13639 2 Dec 2025 Chrome: 143.0.7499.41 < 143.0.7499.41 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-13638 2 Dec 2025 Chrome: 143.0.7499.41 < 143.0.7499.41 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-13637 2 Dec 2025 Chrome: 143.0.7499.41 < 143.0.7499.41 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-13636 2 Dec 2025 Chrome: 143.0.7499.41 < 143.0.7499.41 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-13635 2 Dec 2025 Chrome: 143.0.7499.41 < 143.0.7499.41 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.