Answer in brief
CVE-2026-127138 records a Medium severity (CVSS 6.8) vulnerability in Circumvention of offline barcode revocation check in pretixSCAN. The current sources do not mark it as known exploited. The current feed maps pretix/pretixSCAN Android (generic), pretix/pretixSCAN Desktop (generic), pretix/pretixSCAN iOS (generic), pretix/pretixSCAN Proxy (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps pretix/pretixSCAN Android (generic), pretix/pretixSCAN Desktop (generic), pretix/pretixSCAN iOS (generic), pretix/pretixSCAN Proxy (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| pretix/pretixSCAN Androidgeneric | >=0 <3.5.3 | 3.5.3 |
| pretix/pretixSCAN Desktopgeneric | >=0 <1.23.1 || >=2.0.0 <2.0.1 | 1.23.1, 2.0.1 |
| pretix/pretixSCAN iOSgeneric | >=0 <1.30.1 | 1.30.1 |
| pretix/pretixSCAN Proxygeneric | >=0 <2.7.3 | 2.7.3 |
Published upstream
Nov 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.