{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-127139 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-127139 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-127139 is a medium-severity vulnerability in pretixSCAN Proxy, published on 17 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-127139 and fix it if it is affected.\n\nWhat it is: CVE-2026-127139 is a medium-severity vulnerability in pretixSCAN Proxy, published on 17 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-127139 in the wild and no public exploit code.\n\nAffected product: pretixSCAN Proxy. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-127139/ (Markdown: https://insights.sbomify.com/CVE-2026-127139/index.md)","id":"CVE-2026-127139","markdown":"https://insights.sbomify.com/CVE-2026-127139/index.md","name":"CVE-2026-127139","record":{"aliases":["GHSA-x2hv-fjv4-q826"],"analysis":null,"analysis_generated_by":null,"assigner":"pretix","cpe":[],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-338","name":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)"}],"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.\n\npretixSCAN 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Insecure device token generation in pretixSCAN Proxy","id":"CVE-2026-127139","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"n_vendor_status":0,"next":{"headline":"Server-Side Request Forgery in pretix Widget WordPress plugin","id":"CVE-2026-127140"},"nickname":null,"packages":[],"prev":{"headline":"Circumvention of offline barcode revocation check in pretixSCAN","id":"CVE-2026-127138"},"products":["pretixSCAN Proxy"],"published":"2026-11-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-11-17","vendor_status":[],"vendors":["pretix"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-127139/"}