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

roxy-wi

roxy-wi

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-45569 10 Jun 2026 <= 8.2.6.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-45567 10 Jun 2026 <= 8.2.6.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-45566 10 Jun 2026 <= 8.2.6.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-45565 10 Jun 2026 <= 8.2.6.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-45564 10 Jun 2026 <= 8.2.6.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-45563 10 Jun 2026 <= 8.2.6.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-45561 10 Jun 2026 <= 8.2.6.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-45560 10 Jun 2026 <= 8.2.6.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-45559 10 Jun 2026 <= 8.2.6.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-45558 10 Jun 2026 <= 8.2.6.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-45556 10 Jun 2026 <= 8.2.6.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-45550 10 Jun 2026 <= 8.2.6.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-45549 10 Jun 2026 <= 8.2.6.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-45552 10 Jun 2026 <= 8.2.6.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-33208 24 Apr 2026 < 8.2.6.4 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-33078 24 Apr 2026 < 8.2.6.4 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-33077 24 Apr 2026 < 8.2.6.4 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-33076 24 Apr 2026 < 8.2.6.4 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-33432 20 Apr 2026 <= 8.2.8.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-33431 20 Apr 2026 < 8.2.6.4 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-27811 17 Mar 2026 < 8.2.6.3 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-22265 15 Jan 2026 < 8.2.8.2 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-2024-43804 29 Aug 2024 <= 8.0 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.