{"answers":{"affected":"3 open source packages ship an affected version, including pretix.","exploited":"There is no known exploitation of CVE-2026-9712 in the wild and no public exploit code.","fix":"Upgrade pretix to 2026.4.2 or later.","what":"CVE-2026-9712 is a low-severity vulnerability in pretix, published on 27 May 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-9712 and fix it if it is affected.\n\nWhat it is: CVE-2026-9712 is a low-severity vulnerability in pretix, published on 27 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-9712 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pretix (PyPI): affected all versions; fixed in 2026.4.2\n- pretix (PyPI): affected all versions; fixed in 2026.4.2\n- pretix (PyPI): affected all versions; fixed in 2026.4.2\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-9712/ (Markdown: https://insights.sbomify.com/CVE-2026-9712/index.md)","id":"CVE-2026-9712","markdown":"https://insights.sbomify.com/CVE-2026-9712/index.md","name":"CVE-2026-9712","record":{"aliases":["GHSA-72p9-6vv6-gvqh","PYSEC-2026-2960"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"pretix ticketing system","requires_auth":"low_privilege","summary":"Attackers with valid UUIDs can access unauthorized export files due to missing ownership verification in the pretix API.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"rami.io","cpe":[],"cvss":{"score":3.8,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"When creating an export through the pretix API, API clients are \nreturned an UUID value for their export job (a long, random string like \n35742818-c375-4d15-839f-d49aecce94d6). Using this UUID, the API client \ncan then request the actual file for download. The same kind of UUID is \nused in other places in pretix when temporary files are generated for \ninternal use or download.\n\nOne remaining API endpoint, however, wrongfully did not verify if the\n UUID used for download actually belongs to a file that is supposed to \nbe downloadable and belongs to the correct user. In reality, this is \nhard to exploit because an attacker would need to have access to a valid\n UUID for the file they desire which is unlikely to happen without a \nseparate security problem giving them access to logs etc.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Insecure direct object reference","id":"CVE-2026-9712","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"SQL injection in Product Designer for WooCommerce WordPress | Lumise","id":"CVE-2026-9713"},"packages":[{"ecosystem":"PyPI","fixed":["2026.4.2"],"introduced":["0"],"last_affected":[],"package":"pretix","purl":null,"source":"GHSA-72p9-6vv6-gvqh"},{"ecosystem":"PyPI","fixed":["2026.4.2"],"introduced":["0"],"last_affected":[],"package":"pretix","purl":"pkg:pypi/pretix","source":"GHSA-72p9-6vv6-gvqh"},{"ecosystem":"PyPI","fixed":["2026.4.2"],"introduced":["0"],"last_affected":[],"package":"pretix","purl":"pkg:pypi/pretix","source":"PYSEC-2026-2960"}],"prev":{"headline":"EventON - WordPress Virtual Event Calendar Plugin \u003c= 5.0.11 - Unauthenticated Blind SQL Injection via Search Parameter","id":"CVE-2026-9711"},"products":["pretix"],"published":"2026-05-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"partial"},"state":"PUBLISHED","updated":"2026-05-28","vendors":["pretix"]},"summary":"Attackers with valid UUIDs can access unauthorized export files due to missing ownership verification in the pretix API.","url":"https://insights.sbomify.com/CVE-2026-9712/"}