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

Copeland

Copeland XWEB 300D PRO

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-2026-3037 27 Feb 2026 ≤ 1.12.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-20797 27 Feb 2026 ≤ 1.12.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-22877 27 Feb 2026 ≤ 1.12.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-25037 27 Feb 2026 ≤ 1.12.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-25196 27 Feb 2026 ≤ 1.12.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-20764 27 Feb 2026 ≤ 1.12.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-25721 27 Feb 2026 ≤ 1.12.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-23702 27 Feb 2026 ≤ 1.12.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-24452 27 Feb 2026 ≤ 1.12.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-25105 27 Feb 2026 ≤ 1.12.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-24695 27 Feb 2026 ≤ 1.12.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-20902 27 Feb 2026 ≤ 1.12.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-25109 27 Feb 2026 ≤ 1.12.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-24689 27 Feb 2026 ≤ 1.12.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-20910 27 Feb 2026 ≤ 1.12.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-25195 27 Feb 2026 ≤ 1.12.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-24517 27 Feb 2026 ≤ 1.12.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-20742 27 Feb 2026 ≤ 1.12.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-25111 27 Feb 2026 ≤ 1.12.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-21389 27 Feb 2026 ≤ 1.12.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-24663 27 Feb 2026 ≤ 1.12.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-21718 27 Feb 2026 ≤ 1.12.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-25085 27 Feb 2026 ≤ 1.12.1 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.