Metabase

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 CVE identity is linked to the Lifecycle record Metabase. Use that record for publisher support phases and retirement dates.

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-92813	16 Sep 2026	Metabase: ≤ 0.63.18	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-86116	5 Sep 2026	metabase: 0.57.0 < 0.63.1	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-72900	10 Aug 2026	x.58.0 < x.58.24; x.59.0 < x.59.21; x.60.0 < x.60.17; x.61.0 < x.61.11; x.62.0 < x.62.9; x.63.0 < x.63.5	x.58.24; x.59.21; x.60.17; x.61.11; x.62.9; x.63.5	Update reference ↗
CVE-2026-72899	10 Aug 2026	x.58.0 < x.58.24; x.59.0 < x.59.21; x.60.0 < x.60.17; x.61.0 < x.61.11; x.62.0 < x.62.9; x.63.0 < x.63.5	x.58.24; x.59.21; x.60.17; x.61.11; x.62.9; x.63.5	Update reference ↗
CVE-2026-72898	10 Aug 2026	Metabase: x.58.0 < x.58.24, x.59.0 < x.59.21, x.60.0 < x.60.17, x.61.0 < x.61.11, x.62.0 < x.62.9, x.63.0 < x.63.5	Metabase: x.58.24, x.59.21, x.60.17, x.61.11, x.62.9, x.63.5	Update reference ↗
CVE-2026-50147	15 Jul 2026	>= 1.57.0, < 1.57.19.1; >= 1.58.0, < 1.58.14.1; >= 1.59.0, < 1.59.10; >= 1.60.0, < 1.60.4	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-50148	15 Jul 2026	>= 1.54.0, < 1.54.24; >= 1.55.0, < 1.55.24; >= 1.56.0, < 1.56.25; >= 1.57.0, < 1.57.19; >= 1.58.0, < 1.58.14; >= 1.59.0, < 1.59.10; >= 1.60.0, < 1.60.4	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-59826	9 Jul 2026	>= 1.55.0, < 1.58.15.1; >= 1.59.0, < 1.59.12; >= 1.60.0, < 1.60.6.3; >= 1.61.0, < 1.61.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-2026-59827	9 Jul 2026	>= 1.58.0, < 1.58.15; >= 1.59.0, < 1.59.12; >= 1.60.0, < 1.60.6.3; >= 1.61.0, < 1.61.1.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-33725	27 Mar 2026	< 1.54.22; >= 1.55.0, < 1.55.22; >= 1.56.0, < 1.56.22; >= 1.57.0, < 1.57.16; >= 1.58.0, < 1.58.10; >= 1.59.0, < 1.59.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-27464	21 Feb 2026	< 0.57.13; >= 0.58.x, < 0.58.7	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-22805	12 Jan 2026	>= 0.57.0-beta, < 57.1; >= 0.56.0-beta, < 56.3; < 55.13	No fixed version is explicitly recorded in the structured CVE data.	Update reference ↗
CVE-2025-32382	10 Apr 2025	>= 0.52.12, < 0.52.17.1; >= 1.52.12, < 1.52.17.1; >= 0.53.2.3, < 0.53.9.5; >= 1.53.2.3, < 1.53.9.5; >= 0.54.0.0, < 0.54.1.5; >= 1.54.0.0, < 1.54.1.5	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2025-30371	28 Mar 2025	< 0.52.16.4; < 1.52.16.4; < 0.53.8; < 1.53.8	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2025-27141	24 Feb 2025	>= 1.47.0, < 1.50.36; >= 1.51.0, < 1.51.14; >= 1.52.0, < 1.51.11; >= 1.53.0, < 1.53.2	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2024-55951	16 Dec 2024	>= 1.52.0, < 1.52.2.5	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2023-37470	4 Aug 2023	< 0.43.7.3; >= 0.44.0.0, < 0.44.7.3; >= 0.45.0.0, < 0.45.4.3; >= 0.46.0.0, < 0.46.6.4; >= 1.0.0, < 1.43.7.3; >= 1.44.0.0, < 1.44.7.3; >= 1.45.0.0, < 1.45.4.3; >= 1.46.0.0, < 1.46.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-2023-32680	18 May 2023	< 0.44.7; >= 1.0.0, < 1.44.7; >= 0.45.0, < 0.45.4; >= 1.0.0, < 1.45.4; >= 0.46.0, < 0.46.3; >= 1.0.0, < 1.46.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-2023-23629	28 Jan 2023	< 0.43.7.1; >= 0.44.0-RC1, < 0.44.6.1; >= 0.45.0-RC1, < 0.45.2.1; >= 1.0.0, < 1.43.7.1; >= 1.44.0-RC1, < 1.44.6.1; >= 1.45.0-RC1, < 1.45.2.1	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2023-23628	28 Jan 2023	< 0.43.7.1; >= 0.44.0-RC1, < 0.44.6.1; >= 0.45.0-RC1, < 0.45.2.1; >= 1.0.0, < 1.43.7.1; >= 1.44.0-RC1, < 1.44.6.1; >= 1.45.0-RC1, < 1.45.2.1	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2022-39362	26 Oct 2022	< 0.41.9; >= 0.42.0, < 0.42.6; >= 0.43.0, < 0.43.7; >= 0.44.0, < 0.44.5; >= 1.0.0, < 1.41.9; >= 1.42.0, < 1.42.6; >= 1.43.0, < 1.43.7; >= 1.44.0, < 1.44.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-2022-39361	26 Oct 2022	< 0.41.9; >= 0.42.0, < 0.42.6; >= 0.43.0, < 0.43.7; >= 0.44.0, < 0.44.5; >= 1.0.0, < 1.41.9; >= 1.42.0, < 1.42.6; >= 1.43.0, < 1.43.7; >= 1.44.0, < 1.44.5	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2022-39360	26 Oct 2022	< 0.41.9; >= 0.42.0, < 0.42.6; >= 0.43.0, < 0.43.7; >= 0.44.0, < 0.44.5; >= 1.0.0, < 1.41.9; >= 1.42.0, < 1.42.6; >= 1.43.0, < 1.43.7; >= 1.44.0, < 1.44.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-2022-39359	26 Oct 2022	< 0.41.9; >= 0.42.0, < 0.42.6; >= 0.43.0, < 0.43.7; >= 0.44.0, < 0.44.5; >= 1.0.0, < 1.41.9; >= 1.42.0, < 1.42.6; >= 1.43.0, < 1.43.7; >= 1.44.0, < 1.44.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-2022-39358	26 Oct 2022	< 0.42.6; >= 0.43.0, < 0.43.7; >= 0.44.0, < 0.44.5; >= 1.0.0, < 1.42.6; >= 1.43.0, < 1.43.7; >= 1.44.0, < 1.44.5	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2022-24853	14 Apr 2022	>= 1.40.0, < 1.40.7; >= 0.40.0, < 0.40.7; >= 1.41.0, < 1.41.6; >= 0.41.0, < 0.41.6; >= 1.42.0, < 1.42.3; >= 0.42.0, < 0.42.3	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2022-24854	14 Apr 2022	>= 1.41.0, < 1.41.7; >= 0.41.0, < 0.41.7; >= 1.42.0, < 1.42.4; >= 0.42.0, < 0.42.4	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2022-24855	14 Apr 2022	>= 1.40.0, < 1.40.8; >= 0.40.0, < 0.40.8; >= 1.41.0, < 1.41.7; >= 0.41.0, < 0.41.7; >= 1.42.0, < 1.42.4; >= 0.42.0, < 0.42.4	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2021-41277	17 Nov 2021	metabase: < 0.40.5, >= 1.0.0, < 1.40.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-2018-0697	15 Nov 2018	version 0.29.3 and earlier	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.