Read the docs

Offline QR code revocation check bypass in pretixSCAN

Priority MEDIUM 45Published · Updated

Key facts

Attack vector
Local
Privileges required
None
User interaction
Passive
Attack complexity
Low
Attack requirements
Present
Impact type
—
Confidentiality · integrity · availability
None · High · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

pretixSCAN Android before 3.5.3, pretixSCAN iOS before 1.30.1, pretixSCAN Desktop before 1.23.1 and from 2.0.0 before 2.0.1, and pretixSCAN Proxy before 2.7.3 are affected. A faulty length check when parsing QR codes lets an attacker craft several differently looking QR codes with the same content for one ticket, so they no longer match the revocation list. In offline mode with the pretix signature scheme 1, this lets someone enter with a canceled ticket, which the scanner shows as valid while the server later rejects it.

Written with Claude Haiku 5.5 from the sources below · 2026-11-17

Description from the CNA

pretix provides a mechanism where ticket QR codes are cryptographically signed and can be verified by our pretixSCAN apps in offline mode without any database of valid tickets. pretixSCAN checks the signature to verify that the ticket was issued by the correct pretix event and compares the QR code against a list of revoked QR codes. A QR code becomes revoked when the order is canceled, or the ticket is changed in a way that a new QR code needs to be generated. However, the parsing of the QR code in all of our pretixSCAN apps contained a faulty computation, rendering the check for the correct length of the contents faulty. This way, an attacker is able to craft multiple QR codes for the same ticket which have the same content, but look different and therefore do not match against the revocation list. This does not allow to fabricate entirely new tickets, but it does allow to enter the event with e.g. a canceled ticket. This attack requires pretixSCAN to be scanning in offline mode and the "pretix signature scheme 1" to be used for the event's QR codes. If the attack is executed, the ticket unfortunately shows as valid (green) on the scanner but as invalid (red) on the server since the server later cannot match it to a ticket. We scanned the entire database of scans on pretix Hosted and could not find any traces of this being exploited in the past.

Why it matters now

Fix Fixed pretixSCAN Android (pretix): 3.5.3pretixSCAN iOS (pretix): 1.30.1+2 more products

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
pretixpretixSCAN Androidbefore 3.5.33.5.3Patch availableCNA
pretixpretixSCAN iOSbefore 1.30.11.30.1Patch availableCNA
pretixpretixSCAN Desktopbefore 1.23.1; 2.0.0 to before 2.0.11.23.1, 2.0.1Patch availableCNA
pretixpretixSCAN Proxybefore 2.7.32.7.3Patch availableCNA
  • pretixSCAN Android Vendorpretix Affected before 3.5.3 Fixed in 3.5.3 Patch available CNA
  • pretixSCAN iOS Vendorpretix Affected before 1.30.1 Fixed in 1.30.1 Patch available CNA
  • pretixSCAN Desktop Vendorpretix Affected before 1.23.1; 2.0.0 to before 2.0.1 Fixed in 1.23.1, 2.0.1 Patch available CNA
  • pretixSCAN Proxy Vendorpretix Affected before 2.7.3 Fixed in 2.7.3 Patch available CNA

Remediation

Update pretixSCAN Android to 3.5.3, pretixSCAN iOS to 1.30.1, pretixSCAN Desktop to 1.23.1 or 2.0.1, and pretixSCAN Proxy to 2.7.3.

Written with Claude Haiku 5.5 from the sources below · 2026-11-17

  • Fix · CNA pretixSCAN Android (pretix) Fixed in 3.5.3
  • Fix · CNA pretixSCAN iOS (pretix) Fixed in 1.30.1
  • Fix · CNA pretixSCAN Desktop (pretix) Fixed in 1.23.1, 2.0.1
  • Fix · CNA pretixSCAN Proxy (pretix) Fixed in 2.7.3

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    pretix pretixSCAN Proxy 2.7.3

    2 records Highest priority Priority MEDIUM 1 MEDIUM, 1 LOW

    Other records, highest priority first

    • TI-2026-92520 Predictable device tokens in pretixSCAN ProxyPriority LOW 36

Timeline

  1. 2026-11-17 Threatist record created from CVE-2026-127138

References

  • TI-2024-18268 pretix before 2024.1.1 mishandles file validation. CVSS 3.1CRITICAL 9.8
  • TI-2026-11524 SSRF with API key leak in pretix-oppwa CVSS 4.0CRITICAL 9.0
  • TI-2026-41416 Cross-site scripting in pretix CVSS 4.0HIGH 8.8
  • TI-2026-11523 Session takeover vulnerability CVSS 4.0HIGH 7.7
  • TI-2026-02082 Unsafe variable evaluation in email templates CVSS 4.0HIGH 7.5
  • TI-2026-02081 Unsafe variable evaluation in email templates CVSS 4.0HIGH 7.5
See all 40 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences