# CVE-2026-101271: OAuth credentials not disabled when application is disabled

> Attackers can use OAuth tokens from disabled applications to access data, bypassing intended access controls in the pretix ticketing system.

- **Severity:** Low 2.1 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-5v69-4wqp-6f66

## What is CVE-2026-101271?

CVE-2026-101271 is a low-severity vulnerability in pretix, published on 29 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

OAuth credentials (access tokens) are valid for the entirety of their lifetime, even if the application (OAuth client) they are bound to is manually disabled.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

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


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

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

## Is CVE-2026-101271 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-101271 is a low-severity vulnerability in pretix, published on 29 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-101271 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-101271/ (Markdown: https://insights.sbomify.com/CVE-2026-101271/index.md)
```

## Sources

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

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