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-2025-13634 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-13632 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-13631 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-13630 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-13230 17 Nov 2025 142.0.7444.59 < 142.0.7444.59 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-13229 17 Nov 2025 142.0.7444.59 < 142.0.7444.59 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-13228 17 Nov 2025 142.0.7444.59 < 142.0.7444.59 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-13227 17 Nov 2025 142.0.7444.59 < 142.0.7444.59 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-13226 17 Nov 2025 142.0.7444.59 < 142.0.7444.59 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-13224 17 Nov 2025 142.0.7444.175 < 142.0.7444.175 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-13107 14 Nov 2025 Chrome: 140.0.7339.80 < 140.0.7339.80 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7021 14 Nov 2025 Chrome: 124.0.6367.60 < 124.0.6367.60 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-13178 14 Nov 2025 Chrome: 128.0.6613.84 < 128.0.6613.84 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7017 14 Nov 2025 Chrome: 126.0.6478.182 < 126.0.6478.182 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-9126 14 Nov 2025 Chrome: 127.0.6533.88 < 127.0.6533.88 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-13102 14 Nov 2025 Chrome: 134.0.6998.35 < 134.0.6998.35 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-11919 14 Nov 2025 Chrome: 129.0.6668.58 < 129.0.6668.58 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-11920 14 Nov 2025 Chrome: 130.0.6723.92 < 130.0.6723.92 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-13983 14 Nov 2025 Chrome: 136.0.7103.59 < 136.0.7103.59 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-9479 14 Nov 2025 Chrome: 133.0.6943.141 < 133.0.6943.141 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-13097 14 Nov 2025 Chrome: 136.0.7103.59 < 136.0.7103.59 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-13042 12 Nov 2025 Chrome: 142.0.7444.166 < 142.0.7444.166 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12729 10 Nov 2025 Chrome: 142.0.7444.137 < 142.0.7444.137 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12728 10 Nov 2025 Chrome: 142.0.7444.137 < 142.0.7444.137 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12727 10 Nov 2025 Chrome: 142.0.7444.137 < 142.0.7444.137 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12726 10 Nov 2025 Chrome: 142.0.7444.137 < 142.0.7444.137 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12725 10 Nov 2025 Chrome: 142.0.7444.137 < 142.0.7444.137 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12447 10 Nov 2025 Chrome: 142.0.7444.59 < 142.0.7444.59 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12446 10 Nov 2025 Chrome: 142.0.7444.59 < 142.0.7444.59 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12445 10 Nov 2025 Chrome: 142.0.7444.59 < 142.0.7444.59 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12444 10 Nov 2025 Chrome: 142.0.7444.59 < 142.0.7444.59 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12443 10 Nov 2025 Chrome: 142.0.7444.59 < 142.0.7444.59 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12441 10 Nov 2025 Chrome: 142.0.7444.59 < 142.0.7444.59 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12440 10 Nov 2025 Chrome: 142.0.7444.59 < 142.0.7444.59 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12439 10 Nov 2025 Chrome: 142.0.7444.59 < 142.0.7444.59 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12438 10 Nov 2025 Chrome: 142.0.7444.59 < 142.0.7444.59 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12437 10 Nov 2025 Chrome: 142.0.7444.59 < 142.0.7444.59 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12436 10 Nov 2025 Chrome: 142.0.7444.59 < 142.0.7444.59 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12435 10 Nov 2025 Chrome: 142.0.7444.59 < 142.0.7444.59 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12434 10 Nov 2025 Chrome: 142.0.7444.59 < 142.0.7444.59 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12433 10 Nov 2025 Chrome: 142.0.7444.59 < 142.0.7444.59 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12432 10 Nov 2025 Chrome: 142.0.7444.59 < 142.0.7444.59 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12431 10 Nov 2025 Chrome: 142.0.7444.59 < 142.0.7444.59 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12430 10 Nov 2025 Chrome: 142.0.7444.59 < 142.0.7444.59 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12429 10 Nov 2025 Chrome: 142.0.7444.59 < 142.0.7444.59 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12428 10 Nov 2025 Chrome: 142.0.7444.59 < 142.0.7444.59 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12911 7 Nov 2025 Chrome: 140.0.7339.80 < 140.0.7339.80 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12910 7 Nov 2025 Chrome: 140.0.7339.80 < 140.0.7339.80 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12909 7 Nov 2025 Chrome: 140.0.7339.80 < 140.0.7339.80 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12908 7 Nov 2025 Chrome: 140.0.7339.80 < 140.0.7339.80 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.