# CVE-2026-101274: When pretix is used as the identity provider in a Single-Sign-On (SSO) setup for customer accounts, the system did not properly validate the


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:H/VI:L/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-jgpc-mvf3-4rpj

## What is CVE-2026-101274?

CVE-2026-101274 is a medium-severity vulnerability, published on 28 Oct 2026. 

### Official description

When pretix is used as the identity provider in a Single-Sign-On (SSO) setup for customer accounts, the system did not properly validate the `response_type` requested in an authorization request against the configured grant type of the SSO client. This means that if an SSO client was configured to only allow the `code` response type, which requires knowledge of the client secret to use and would wrongfully send a response type like `id_token`, it would receive back a valid token. Exploiting this requires the attacker to run JavaScript on the page specified by `redirect_uri`, which must be from a list specified in the client configuration.

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


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

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

## Is CVE-2026-101274 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-101274 is a medium-severity vulnerability, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-101274 in the wild and no public exploit code.

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-101274/ (Markdown: https://insights.sbomify.com/CVE-2026-101274/index.md)
```

## Sources

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

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