Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY2455 SECURITY RECORDS

Google Inc.

Android

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 android, 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-28604 8 Sep 2026 Android: 17, 16-qpr2, 16, 15, 14 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-2026-28603 8 Sep 2026 Android: 17, 16-qpr2, 16, 15, 14 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-2026-28602 8 Sep 2026 Android: 17, 16-qpr2, 16, 15, 14 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-2026-28600 8 Sep 2026 Android: 17, 16-qpr2, 16, 15 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-2026-28599 8 Sep 2026 Android: 17, 16-qpr2, 16 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-2026-28596 8 Sep 2026 Android: 16-qpr2, 16, 15, 14 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-28594 8 Sep 2026 Android: 17, 16-qpr2 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-2026-28593 8 Sep 2026 Android: 17, 16-qpr2, 16, 15, 14 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-28590 8 Sep 2026 Android: 16-qpr2, 16, 15, 14 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-28584 8 Sep 2026 Android: 17, 16-qpr2 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-2026-28583 8 Sep 2026 Android: 16-qpr2, 16, 15, 14 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-28582 8 Sep 2026 Android: 17, 16-qpr2, 16, 15, 14 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-2026-28572 8 Sep 2026 Android: 16-qpr2 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-0084 8 Sep 2026 Android: 16-qpr2, 16 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-0065 8 Sep 2026 Android: 16-qpr2, 16, 15, 14 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-0054 8 Sep 2026 Android: 16-qpr2, 16, 15, 14 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2025-36940 24 Aug 2026 Android: F30.1.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0163 4 Aug 2026 Android: Android kernel No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-28573 18 Jun 2026 14; 16 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0063 17 Jun 2026 17 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-28587 17 Jun 2026 17 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-28615 17 Jun 2026 17 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0083 17 Jun 2026 17 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0082 17 Jun 2026 17 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0081 17 Jun 2026 17 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0071 17 Jun 2026 17 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-28575 17 Jun 2026 17 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0064 17 Jun 2026 17 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0092 17 Jun 2026 17 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0068 17 Jun 2026 17 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0057 17 Jun 2026 17 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0019 17 Jun 2026 Android: 17 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-48643 17 Jun 2026 Android: 17 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-48640 17 Jun 2026 Android: 17 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-48617 17 Jun 2026 Android: 17 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-48571 17 Jun 2026 Android: 17 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0165 16 Jun 2026 Android: Android kernel No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0164 16 Jun 2026 Android kernel No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0162 16 Jun 2026 Android kernel No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0161 16 Jun 2026 Android kernel No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0160 16 Jun 2026 Android kernel No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0158 16 Jun 2026 Android: Android kernel No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0157 16 Jun 2026 Android: Android kernel No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0156 16 Jun 2026 Android: Android kernel No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0155 16 Jun 2026 Android: Android kernel No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0154 16 Jun 2026 Android kernel No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0153 16 Jun 2026 Android kernel No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0152 16 Jun 2026 Android kernel No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0151 16 Jun 2026 Android kernel No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0150 16 Jun 2026 Android kernel 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.