ROOT-OS-UBUNTU-2404-CVE-2025-39945 CVE-2025-39945 in rootio-linux - Patched by Root

Root has patched CVE-2025-39945 in the rootio-linux package for Root:Ubuntu:24.04. Multiple fixed versions available...

ROOT-OS-UBUNTU-2404-CVE-2026-43362 CVE-2026-43362 in rootio-linux - Patched by Root

Root has patched CVE-2026-43362 in the rootio-linux package for Root:Ubuntu:24.04. Multiple fixed versions available...

ROOT-OS-UBUNTU-2404-CVE-2025-37861 CVE-2025-37861 in rootio-linux - Patched by Root

Root has patched CVE-2025-37861 in the rootio-linux package for Root:Ubuntu:24.04. Multiple fixed versions available...

ROOT-OS-UBUNTU-2404-CVE-2025-21776 CVE-2025-21776 in rootio-linux - Patched by Root

Root has patched CVE-2025-21776 in the rootio-linux package for Root:Ubuntu:24.04. Multiple fixed versions available...

ROOT-OS-UBUNTU-2404-CVE-2025-40347 CVE-2025-40347 in rootio-linux - Patched by Root

Root has patched CVE-2025-40347 in the rootio-linux package for Root:Ubuntu:24.04. Multiple fixed versions available...

ROOT-OS-UBUNTU-2404-CVE-2025-39763 CVE-2025-39763 in rootio-linux - Patched by Root

Root has patched CVE-2025-39763 in the rootio-linux package for Root:Ubuntu:24.04. Multiple fixed versions available...

ROOT-OS-UBUNTU-2404-CVE-2025-21773 CVE-2025-21773 in rootio-linux - Patched by Root

Root has patched CVE-2025-21773 in the rootio-linux package for Root:Ubuntu:24.04. Multiple fixed versions available...

ROOT-OS-UBUNTU-2404-CVE-2026-31578 CVE-2026-31578 in rootio-linux - Patched by Root

Root has patched CVE-2026-31578 in the rootio-linux package for Root:Ubuntu:24.04. Multiple fixed versions available...

ROOT-OS-UBUNTU-2404-CVE-2025-21830 CVE-2025-21830 in rootio-linux - Patched by Root

Root has patched CVE-2025-21830 in the rootio-linux package for Root:Ubuntu:24.04. Multiple fixed versions available...

ROOT-OS-UBUNTU-2404-CVE-2026-23056 CVE-2026-23056 in rootio-linux - Patched by Root

Root has patched CVE-2026-23056 in the rootio-linux package for Root:Ubuntu:24.04. Multiple fixed versions available...

ROOT-OS-UBUNTU-2404-CVE-2026-23091 CVE-2026-23091 in rootio-linux - Patched by Root

Root has patched CVE-2026-23091 in the rootio-linux package for Root:Ubuntu:24.04. Multiple fixed versions available...

ROOT-OS-UBUNTU-2404-CVE-2026-23468 CVE-2026-23468 in rootio-linux - Patched by Root

Root has patched CVE-2026-23468 in the rootio-linux package for Root:Ubuntu:24.04. Multiple fixed versions available...

ROOT-OS-UBUNTU-2404-CVE-2025-38310 CVE-2025-38310 in rootio-linux - Patched by Root

Root has patched CVE-2025-38310 in the rootio-linux package for Root:Ubuntu:24.04. Multiple fixed versions available...

MINI-XMG8-F3QM-VF2J

Bulletin has no description...

MINI-H6W5-3HGV-4Q7F

Bulletin has no description...

CVE-2026-18029

Our payment integration with GiroCheckout did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment...

CVE-2026-18029

The CVE-2026-18029 entry is tied to the pretix-girosolution payment integration. Affected component: payment status validation in GiroCheckout flow. Root cause: insufficient validation of payment status responses, enabling an attacker to reuse a successful status for one payment with a different ...

CVE-2026-18029

Our payment integration with GiroCheckout did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment...

EUVD-2026-49752

Our payment integration with GiroCheckout did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment...

CVE-2026-18029 Insufficient validation of payment status in pretix-girosolution

Our payment integration with GiroCheckout did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment...