Skip to main content
Menu
CVEs

CVE

pretixSCAN Proxy predictable device tokens allow connection hijacking

CVE-2026-127139EUVD-2026-126989GHSA-X2HV-FJV4-Q826

CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U

4.4MediumCNA
Exploited
No known exploitation
Fix
Fixed in 2.7.3
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 2.7.3.

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

Summary

The pretixSCAN Proxy does not use a secure random generator for the initialization tokens and API keys that link pretixSCAN devices to the proxy, so tokens can be predicted more easily. An attacker with local access and low-privilege login could use some known tokens to guess others, which could let them compromise the device connections.

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

Original description

pretixSCAN Proxy does not use a secure random generator to generate initialization tokens and API keys for the connection between pretixSCAN devices and the pretixSCAN Proxy. This could allow a skilled attacker with access to at least some of the tokens to predict the value of other tokens more easily.

pretixSCAN is usually used on local networks and the level of exposure heavily depends on the structure of that network. If you want to be extra careful, it might make sense to reconnect your devices to the proxy after the update.

cve.now Index

5Pcve.now Index 5 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.4/10CVSS 4.4, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 60 if added to CISA KEV
  • Would score about 55 if CISA's SSVC rates exploitation active
  • Would score about 27 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 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-127139 (Insecure device token generation in pretixSCAN Proxy), 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-127139 (entry last updated 2026-11-17):
Affected:
- pretix pretixSCAN Proxy: fixed in 2.7.3
Fixed versions: 2.7.3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-127139 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-127139 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-127139
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-127139"}.

Timeline

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

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

  4. Record last updated

Affected versions

  • pretix pretixSCAN Proxy

    fixed in 2.7.3

Evidence 3

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

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-127139

Is CVE-2026-127139 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-127139?

pretixSCAN Proxy: before 2.7.3.Source: cve.now feed data

How do I fix CVE-2026-127139?

Upgrade to a fixed version: 2.7.3.Source: cve.now feed data

More CVEs