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

Azure Access Technology

BLU-IC2

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.

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-12603 1 Nov 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12602 1 Nov 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12601 1 Nov 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12600 1 Nov 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12599 1 Nov 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12554 31 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12553 31 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12552 31 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12517 30 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12516 30 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12515 30 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12479 29 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12478 29 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12477 29 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12476 29 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12425 28 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12424 28 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12423 28 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12422 28 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12365 27 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12364 27 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12363 27 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12285 26 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12284 26 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12275 26 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12278 26 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12221 25 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12220 25 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12219 25 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12218 25 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12217 25 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12216 25 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12176 24 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12114 23 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12104 23 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12031 21 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12001 20 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-11925 17 Oct 2025 ≤ 1.19.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-11832 15 Oct 2025 1.0 ≤ 1.19.5 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.