# CVE-2026-101269: Incorrect session validation for API-uploaded files

> Incorrect session validation for API-uploaded files in pretix allows bypassing uploader authentication, though risk is low due to UUIDs and short expiration.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-2qwc-826w-vxph

## What is CVE-2026-101269?

CVE-2026-101269 is a low-severity authentication bypass vulnerability in pretix, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The mechanism binding API-uploaded files to the uploader's authentication method is not working correctly and the same session token is used for all token-based API users. Since API-uploaded files are refered to by randomly generated UUIDs and only exist for a day, there is virtually no risk, but it renders the added protection mechanism useless.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-101269 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-101269 is a low-severity authentication bypass vulnerability in pretix, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-101269 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-101269/ (Markdown: https://insights.sbomify.com/CVE-2026-101269/index.md)
```

## Sources

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

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