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
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2026.6.4, 2026.7.3, 2026.8.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
pretix, the open-source event ticketing software, is affected when it acts as the identity provider for Single-Sign-On customer accounts. In this setup, it failed to check that the requested response type matched the client's configured grant type, so it could issue tokens that bypass the intended restrictions.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original 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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- pretix
fixed in 2026.6.4; From 2026.7.0 · fixed in 2026.7.3; From 2026.8.0 · fixed in 2026.8.1