# CVE-2026-101275: Pretix payment status validation bypass in Adyen integration

Source: https://junglewise.ai/threats/cve-2026-101275-our-payment-integration-with-adyen-did-not-properly-validate  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-10. Updated: 2026-11-10  
License: CC BY 4.0 with a link back

CVE-2026-101275 · Severity: info · Published 2026-11-10

Pretix, a ticketing and event management platform, failed to properly validate payment status responses from the Adyen payment processor. An attacker could replay a successful payment confirmation from one transaction to obtain tickets for a different purchase, bypassing the need to actually pay for multiple orders.

Technologies: [Pretix](https://junglewise.ai/threats/technologies/pretix-pretix). Vendors: [Pretix](https://junglewise.ai/threats/vendors/pretix).

## Quick answers

**Is CVE-2026-101275 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-101275 being exploited in the wild.

**How severe is CVE-2026-101275?** Informational severity, published 10 November 2026.

**Which products and versions are affected?** Pretix Pretix.

**Is there a fix for CVE-2026-101275?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-101275 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-101275?** Check whether you run Pretix. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is a payment status response validation bypass in Pretix's Adyen payment integration. An attacker can supply a legitimate payment status response from one completed payment to the system as if it applies to a different payment, allowing them to claim fulfillment (ticket issuance) without payment. This requires network access to the payment callback mechanism but no authentication or special preconditions beyond initiating a purchase.

## Affected products

- Pretix Pretix

## Timeline

- 2026-11-10: disclosed

## References

- [https://pypi.python.org/](https://pypi.python.org/)
- [https://pretix.eu/about/en/blog/20261110-adyen/](https://pretix.eu/about/en/blog/20261110-adyen/)

## Related threats

- [pretix missing permission check in ticket layout API](https://junglewise.ai/threats/cve-2026-125744-our-api-endpoint-for-changing-ticket-layouts-did-not-properly)
- [pretix improper validation of OpenID Connect response_type in SSO](https://junglewise.ai/threats/cve-2026-101274-when-pretix-is-used-as-the-identity-provider-in-a-single-sign-on)
- [pretix gift card ID enumeration and account credit increase](https://junglewise.ai/threats/cve-2026-101273-some-of-our-api-endpoints-allowed-to-create-order-payments)
- [pretix session validation bypass in API-created shredder exports](https://junglewise.ai/threats/cve-2026-101272-the-mechanism-binding-files-generated-during-a-shredding-process)
- [Pretix OAuth access token revocation failure](https://junglewise.ai/threats/cve-2026-101271-oauth-credentials-access-tokens-are-valid-for-the-entirety-of)