# CVE-2026-11764: Data exposed without proper permission

> Attackers can export gift card secrets without permission, bypassing access controls and exposing sensitive data in pretix event ticketing systems.

- **Severity:** Low 3.6 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2026
- **Updated:** 9 Jun 2026
- **Also known as:** GHSA-m6hc-99rm-c9wc

## What is CVE-2026-11764?

CVE-2026-11764 is a low-severity missing authorization vulnerability in pretix, published on 9 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

When creating an export of all reusable media, the secrets of connected 
gift cards were included in the export even if the user creating the 
export does not have permission to view gift cards. This is inconsistent
 with the UI and API where only the first letters of the gift card 
secret are shown. Therefore, it allows circumventing a permission 
boundary.

Weakness: CWE-280 (Improper Handling of Insufficient Permissions or Privileges)

## Which versions are affected by CVE-2026-11764?


## How do I fix CVE-2026-11764?

No fix has been published for CVE-2026-11764 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-11764 being exploited?

There is no known exploitation of CVE-2026-11764 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-11764 and fix it if it is affected.

What it is: CVE-2026-11764 is a low-severity missing authorization vulnerability in pretix, published on 9 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-11764 in the wild and no public exploit code.

Affected product: pretix. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-11764/ (Markdown: https://insights.sbomify.com/CVE-2026-11764/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-11764
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-11764
- OSV: https://osv.dev/vulnerability/CVE-2026-11764

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-11764/
Summaries are generated and may contain mistakes; the official description above is the record.