# CVE-2026-127138: Circumvention of offline barcode revocation check in pretixSCAN


- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-w7wc-82mm-ff4g

## What is CVE-2026-127138?

CVE-2026-127138 is a medium-severity vulnerability in pretixSCAN Android, published on 17 Nov 2026. 

### Official description

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.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-127138?


## How do I fix CVE-2026-127138?

No fix has been published for CVE-2026-127138 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-127138 being exploited?

There is no known exploitation of CVE-2026-127138 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-127138 and fix it if it is affected.

What it is: CVE-2026-127138 is a medium-severity vulnerability in pretixSCAN Android, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-127138 in the wild and no public exploit code.

Affected product: pretixSCAN Android. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-127138/ (Markdown: https://insights.sbomify.com/CVE-2026-127138/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-127138
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-127138
- OSV: https://osv.dev/vulnerability/CVE-2026-127138

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-127138/
Summaries are generated and may contain mistakes; the official description above is the record.
