pretix, the open-source ticketing system made by pretix GmbH in Heidelberg, published two posts on its blog on 10 November 2026. The first is security release 2026.9.1, which fixes a medium-rated flaw in its Adyen payment plugin that could let one payment unlock several valid tickets, plus a low-rated permissions gap in the ticket layout API. The second announces the biggest change to how pretix asks buyers for information in years. Questions become data fields grouped into questionnaires, and the switch, planned for 8 December 2026, breaks parts of the REST API. Customers on pretix Hosted already have the security fixes. If you self-host pretix, or if you run your own code against the pretix API, both posts need action. This report is based on those two posts; Event Tech News has not tested either change.
The Adyen payment flaw
pretix says its Adyen integration did not properly check the payment status responses it received. Someone could take the success response from one payment and present it for a different order, which would give them several valid tickets for the price of one. The issue is tracked as CVE-2026-101275 and was reported by Digant Prajapati. pretix rates it medium because no personal data is exposed and, in its words, exploitation on a large scale would probably be noticed. All supported versions were affected, and the fix is pretix-adyen 1.5.4.
If you take payments through Adyen, it is worth comparing paid orders against your Adyen settlement reports for recent on-sales, since a ticket bought this way would look like an ordinary paid order in pretix. Shops that use Stripe, Mollie, PayPal or bank transfer are not affected by this particular issue.
The ticket layout permission gap
The second issue, CVE-2026-125744, reported by Immanuel Tikhonov, sat in the API endpoint for changing ticket layouts. It did not check the permissions of the user or API token making the request, so someone with read-only access to an event could change how its tickets look. pretix rates this low because the attacker already needs access to the event and layouts hold no sensitive data. It still matters if you hand read-only API tokens to agencies, box office partners or reporting tools.
Which versions fix it
pretix has released fixes for its last three stable branches on PyPI, 2026.9.1, 2026.8.2 and 2026.7.4, alongside pretix-adyen 1.5.4. It says anyone on a version older than 2026.7 should upgrade to a recent release now. This is the second security release in a fortnight, after 2026.8.1 fixed three flaws on 28 October, so if you skipped that update you can take both fixes in one move to 2026.9.1.
What questionnaires add for organisers
Today a pretix question is a custom field attached to products and asked for every ticket, with attendee name, email, company and address handled separately as “personalised tickets”. Under the new model, pretix says you will be able to
- ask a question once per order rather than once per ticket, which helps with group bookings where you only need the information one time
- group questions into questionnaires and attach a questionnaire to many products at once, instead of ticking products on each question
- make the same field required in one questionnaire and optional in another, so a company name can be mandatory on business tickets and optional elsewhere while remaining one field for badges and exports
- change a question’s label and help text per questionnaire, including system fields such as name and email
- ask for part of an address, such as postcode and country only
- place blocks of explanatory text between questions
- ask some questions only on particular sales channels
Existing questions are converted automatically into data fields, and pretix will create questionnaires that reproduce your current setup, so your checkout should look the same on the day of the change. pretix also says pretixSCAN and pretixPOS keep working without an app update, though you will need new versions of both apps, due before the rollout, to use the new features at the door and the till.
What breaks in the API
The questions resource becomes read-only and deprecated. Code that creates or edits questions through the API will stop working and has to move to the new data fields and questionnaires resources. The event settings for which attendee details are asked and required (the attendee_*_asked and attendee_*_required properties) disappear. A product’s personalised flag stops being a real setting, returns a value worked out from its questionnaires, and now defaults to false. Order positions may also carry extra answer entries with generated IDs for system fields. pretix adds that the read-only questions endpoints return HTTP 410 on any event whose questionnaires cannot be expressed in the old model, for example when one field appears in two questionnaires with different labels.
Checking in tickets, creating orders and reading order positions do not change in incompatible ways, and the question options endpoints are renamed to data field options with the old addresses kept for a while. pretix expects only a small number of customers to be affected, mostly in processes that are not business critical, and its API documentation already describes the new resources.
What to do
If you self-host, upgrade to 2026.9.1 (or 2026.8.2 or 2026.7.4 on older branches) and update pretix-adyen to 1.5.4 if you use it. Then check who holds read-only API tokens for your events. If you have built anything on the pretix API, such as a CRM sync, a registration form or a badge workflow, search it for calls that write questions or read the attendee settings before 8 December, and test against the new documentation. pretix says it will update the blog post if the rollout date moves. If you are comparing ticketing platforms on how they handle buyer questions, Hi.Events recently added follow-up and eligibility questions in its own open-source release.
Sources
- pretix blog, Security release 2026.9.1 of pretix and pretix-adyen plugin (10 November 2026)
- pretix blog, Upcoming feature and API change, Questionnaires (10 November 2026)
Sources checked 12 November 2026. Details are taken from pretix’s own posts. Event Tech News has not tested these changes.
- pretix in the vendor directory, with its pricing and plans
- Kiosk check-in redesign arrives with pretix 2026.8.0
- How pretixSCAN handles offline check-in
- Questions to ask about event app integrations
- Choosing event registration software
- Registration and ticketing software, including Tito and Ticket Tailor, plus pretalx for calls for papers
Companies in this story
- pretixSell tickets, run the door and print badges from one backend with no monthly fee on the hosted service, which charges 2.5% per paid ticket, never more than €15, excluding VAT.
- Hi.EventsYou can sell tickets with no monthly fee and pay nothing on free events, because the 1.25% + $0.60 fee on a paid ticket can go to the buyer, or self-host the open-source version free.
- TitoYou get registration and ticketing for technology, developer and B2B conferences without a subscription, with an embeddable widget, developer documentation and a standard fee of 3% per paid ticket.
- Ticket TailorSell tickets from £0.22 each (+ VAT) on prepaid credits or £0.60 pay as you go, take payouts straight into your own processor account, and scan entry with a free iOS and Android app.
- pretalxpretalx is open-source call for papers and conference scheduling software from Weinheim, Germany, hosted from EUR 199 per event or free to self-host.







