incus

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 incus, 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

CVE	Published	Affected versions	Fixed version information	Publisher evidence
CVE-2026-63343	21 Aug 2026	incus: < 7.3.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-63125	21 Aug 2026	incus: < 7.3.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-62941	21 Aug 2026	incus: < 7.3.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-62940	21 Aug 2026	incus: < 7.3.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-62867	21 Aug 2026	incus: < 7.3.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-62313	21 Aug 2026	incus: < 7.3.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-55622	21 Aug 2026	incus: < 7.2.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-55621	21 Aug 2026	incus: < 7.2.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-48769	21 Aug 2026	incus: < 7.2.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-48755	21 Aug 2026	incus: < 7.2.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-48754	21 Aug 2026	incus: < 7.1.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-48753	21 Aug 2026	incus: < 7.1.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-48752	21 Aug 2026	incus: < 7.2.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-48751	21 Aug 2026	incus: < 7.2.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-48750	21 Aug 2026	incus: < 7.2.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-48749	21 Aug 2026	incus: < 7.2.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-47753	21 Aug 2026	incus: < 7.1.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-48756	21 Aug 2026	incus: < 7.1.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-41685	7 May 2026	< 7.0.0	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-41684	7 May 2026	< 7.0.0	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-41648	7 May 2026	< 7.0.0	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-41647	7 May 2026	< 7.0.0	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-40251	6 May 2026	< 7.0.0	7.0.0.	Update reference ↗
CVE-2026-40243	6 May 2026	< 7.0.0	7.0.0.	Update reference ↗
CVE-2026-40197	6 May 2026	< 7.0.0	7.0.0.	Update reference ↗
CVE-2026-40195	6 May 2026	< 7.0.0	7.0.0.	Update reference ↗
CVE-2026-35527	5 May 2026	< 7.0.0	7.0.0.	Update reference ↗
CVE-2026-33945	26 Mar 2026	< 6.23.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-33898	26 Mar 2026	< 6.23.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-33897	26 Mar 2026	< 6.23.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-33743	26 Mar 2026	< 6.23.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-33711	26 Mar 2026	< 6.23.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-33542	26 Mar 2026	< 6.23.0	No fixed version is explicitly recorded in the structured CVE data.	Update reference ↗
CVE-2026-23954	22 Jan 2026	>= 6.1.0, <= 6.20.0; <= 6.0.5	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-23953	22 Jan 2026	>= 6.1.0, <= 6.20.0; <= 6.0.5	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-2025-64507	10 Nov 2025	< 6.0.6; >= 6.1.0, < 6.19.0	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-2025-52890	25 Jun 2025	>= 6.12, <= 6.13	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2025-52889	25 Jun 2025	>= 6.12, <= 6.13	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.