Skip to main content
Menu
CVEs

CVE

Revocation check bypass in offline QR parsing

CVE-2026-127138EUVD-2026-126988GHSA-W7WC-82MM-FF4G

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

6.8MediumCNA
Exploited
No known exploitation
Fix
Fixed in pretixSCAN Android 3.5.3 · pretixSCAN iOS 1.30.1 · pretixSCAN Desktop 1.23.1, 2.0.1 · pretixSCAN Proxy 2.7.3
Who is exposed
Not reported

Do first: Upgrade to a fixed version: pretixSCAN Android 3.5.3 · pretixSCAN iOS 1.30.1 · pretixSCAN Desktop 1.23.1, 2.0.1 · pretixSCAN Proxy 2.7.3.

Published
Last modified
Reference
Last checked
7/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

pretixSCAN on Android, iOS, Desktop, and Proxy has a flaw in how it parses ticket QR codes. A local attacker who can present a crafted QR code can get a revoked ticket, such as a canceled one, accepted as valid at the entrance, which requires a user action and offline scanning mode.

Written by a model from the sources below. Verify against them.

Original 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.

cve.now Index

7Pcve.now Index 7 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.8/10CVSS 6.8
  • No patch0/5No signal

What would change the score

  • Would score about 62 if added to CISA KEV
  • Would score about 57 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: pretixSCAN Android 3.5.3 · pretixSCAN iOS 1.30.1 · pretixSCAN Desktop 1.23.1, 2.0.1 · pretixSCAN Proxy 2.7.3.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-127138 (Circumvention of offline barcode revocation check in pretixSCAN), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-127138 (entry last updated 2026-11-17):
Affected:
- pretix pretixSCAN Android: fixed in 3.5.3
- pretix pretixSCAN iOS: fixed in 1.30.1
- pretix pretixSCAN Desktop: fixed in 1.23.1; from 2.0.0, fixed in 2.0.1
- pretix pretixSCAN Proxy: fixed in 2.7.3
Fixed versions: 3.5.3, 1.30.1, 1.23.1, 2.0.1, 2.7.3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-127138 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-127138 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://pretix.eu/about/en/blog/20261117-release-2026-9-2-pretixscan-wordpress-widget/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-127138
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-127138"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • pretix pretixSCAN Android

    fixed in 3.5.3

  • pretix pretixSCAN iOS

    fixed in 1.30.1

  • pretix pretixSCAN Desktop

    fixed in 1.23.1; From 2.0.0 · fixed in 2.0.1

  • pretix pretixSCAN Proxy

    fixed in 2.7.3

Evidence 3

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Link

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-127138

Is CVE-2026-127138 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-127138?

pretixSCAN Android: before 3.5.3. pretixSCAN iOS: before 1.30.1. pretixSCAN Desktop: before 1.23.1; from 2.0.0 before 2.0.1. pretixSCAN Proxy: before 2.7.3.Source: cve.now feed data

How do I fix CVE-2026-127138?

Upgrade to a fixed version: pretixSCAN Android 3.5.3 · pretixSCAN iOS 1.30.1 · pretixSCAN Desktop 1.23.1, 2.0.1 · pretixSCAN Proxy 2.7.3.Source: cve.now feed data

More CVEs