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

pretix GmbH

pretix

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

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-101271 29 Sep 2026 pretix: 0.0 < 2026.5.5, 2026.6.0 < 2026.6.2, 2026.7.0 < 2026.7.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-101270 29 Sep 2026 pretix: 0.0 < 2026.5.5, 2026.6.0 < 2026.6.2, 2026.7.0 < 2026.7.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-101269 29 Sep 2026 pretix: 0.0 < 2026.5.5, 2026.6.0 < 2026.6.2, 2026.7.0 < 2026.7.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-101268 29 Sep 2026 pretix: 0.0 < 2026.5.5, 2026.6.0 < 2026.6.2, 2026.7.0 < 2026.7.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-101267 29 Sep 2026 pretix: 0.0 < 2026.5.5, 2026.6.0 < 2026.6.2, 2026.7.0 < 2026.7.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-101266 29 Sep 2026 pretix: 0.0 < 2026.5.5, 2026.6.0 < 2026.6.2, 2026.7.0 < 2026.7.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-18028 28 Jul 2026 < 2026.4.6; 2026.5.0 < 2026.5.4; 2026.6.0 < 2026.6.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13602 1 Jul 2026 4.14.0 < 2026.3.5; 2026.4.0 < 2026.4.5; 2026.5.0 < 2026.5.3; < 2.5.7; < 1.4.4; < 1.5.3; < 1.4.3; < 1.0.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-57532 25 Jun 2026 < 2026.3.4; 2026.4.0 < 2026.4.4; 2026.5.0 < 2026.5.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-57533 25 Jun 2026 < 2026.3.4; 2026.4.0 < 2026.4.4; 2026.5.0 < 2026.5.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-57535 25 Jun 2026 < 2026.3.4; 2026.4.0 < 2026.4.4; 2026.5.0 < 2026.5.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13225 25 Jun 2026 < 2026.3.4; 2026.4.0 < 2026.4.4; 2026.5.0 < 2026.5.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-11764 9 Jun 2026 2024.1.0 < 2026.3.0; 2026.3.0 < 2026.4.0; 2026.4.0 < 2026.5.0; 2026.5.0 < 2026.6.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-9712 27 May 2026 2024.10.0 < 2026.2.0; 2026.2.0 < 2026.3.0; 2026.3.0 < 2026.4.0; 2026.4.0 < 2026.5.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-5600 8 Apr 2026 2025.10.0 < 2026.1.2; 2026.2.0 < 2026.2.1; 2026.3.0 < 2026.3.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-2415 16 Feb 2026 4.16.0 < 2025.9.0; 2025.9.0 < 2025.10.0; 2025.10.0 < 2026.1.0; 2026.1.0 < 2026.1.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 ↗
CVE-2025-14881 19 Dec 2025 1.0.0 < 2025.8.0; 2025.8.0 < 2025.9.0; 2025.9.0 < 2025.10.0; 2025.10.0 < 2025.11.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-13742 27 Nov 2025 1.0.0 < 2025.7.0; 2025.7.0 < 2025.8.0; 2025.8.0 < 2025.9.0; 2025.9.0 < 2025.10.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8113 23 Aug 2024 ≤ 2024.7.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.