CVE-LINKED INVENTORY17 SECURITY RECORDS

Saleor

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 saleor, 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-44472	18 Aug 2026	saleor: >= 2.10.0rc1, < 3.21.67, >= 3.22.0-a.0, < 3.22.63, >= 3.23.0-a.0, < 3.23.22	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-48744	18 Aug 2026	saleor: >= 3.14.67, < 3.21.67, >= 3.22.0-a.0, < 3.22.63, >= 3.23.0-a.0, < 3.23.22	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-39851	8 Apr 2026	>= 2.10.0, < 3.20.118; >= 3.21.0-a.0, < 3.21.54; >= 3.22.0-a.0, < 3.22.47; >= 3.23.0-a.0, < 3.23.0a3	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-35407	8 Apr 2026	>= 2.10.0, < 3.20.118; >= 3.21.0-a.0, < 3.21.54; >= 3.22.0-a.0, < 3.22.47; >= 3.23.0-a.0, < 3.23.0a3	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-35401	8 Apr 2026	>= 2.0.0, < 3.20.118; >= 3.21.0-a.0, < 3.21.54; >= 3.22.0-a.0, < 3.22.47; >= 3.23.0-a.0, < 3.23.0a3	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-33756	8 Apr 2026	>= 2.0.0, < 3.20.118; >= 3.21.0-a.0, < 3.21.54; >= 3.22.0-a.0, < 3.22.47; >= 3.23.0-a.0, < 3.23.0a3	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-24136	23 Jan 2026	>= 3.22.0-a.0, < 3.22.29; >= 3.21.0-a.0, < 3.21.45; >= 3.2.0, < 3.20.110	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-23499	21 Jan 2026	>= 3.2.0, < 3.22.27; >= 3.1.0, < 3.21.43; >= 3.0.0, < 3.20.108	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-22849	21 Jan 2026	>= 3.2.0, < 3.22.27; >= 3.1.0, < 3.21.43; >= 3.0.0, < 3.20.108	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-58442	9 Sep 2025	>= 3.21.0, < 3.21.16	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2024-31205	8 Apr 2024	>= 3.10.0, < 3.14.64; >= 3.15.0, < 3.15.39; >= 3.16.0, < 3.16.39; >= 3.17.0, < 3.17.35; >= 3.18.0, < 3.18.31; >= 3.19.0, < 3.19.19	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-29888	27 Mar 2024	>= 3.14.56, < 3.14.61; >= 3.15.31, < 3.15.37; >= 3.16.27, < 3.16.34; >= 3.17.25, < 3.17.32; >= 3.18.19, < 3.18.28; >= 3.19.5, < 3.19.15	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-32694	25 May 2023	>= 2.11.0, < 3.7.68; >= 3.8.0, < 3.8.40; >= 3.9.0, < 3.9.49; >= 3.10.0, < 3.10.36; >= 3.11.0, < 3.11.35; >= 3.12.0, < 3.12.25; >= 3.13.0, < 3.13.16	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-26052	2 Mar 2023	>= 2.0.0, < 3.1.48; >= 3.11.0, < 3.11.12; >= 3.10.0, < 3.10.14; >= 3.9.0, < 3.9.27; >= 3.8.0, < 3.8.30; >= 3.7.0, < 3.7.59	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2023-26051	2 Mar 2023	>= 2.0.0, < 3.1.48; >= 3.11.0, < 3.11.12; >= 3.10.0, < 3.10.14; >= 3.9.0, < 3.9.27; >= 3.8.0, < 3.8.30; >= 3.7.0, < 3.7.59	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-39275	6 Oct 2022	>= 2.0.0, < 3.1.24; >= 3.2.0, < 3.2.14; >= 3.3.0, < 3.3.26; >= 3.4.0, < 3.4.24; >= 3.5.0, < 3.5.23; >= 3.6.0, < 3.6.18; >= 3.7.0, < 3.7.17	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-2019-1010304	15 Jul 2019	Issue was introduced by merge commit: e1b01bad0703afd08d297ed3f1f472248312cc9c. This commit was released as part of 2.0.0 release [fixed: 2.3.1]	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 ↗

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.