CVE-2026-101275: Our payment integration with Adyen did not properly validate payment status responses
Source GCVE Database
Not known to be exploited · CVSS 6.3 Medium : upgrade to 1.5.4 when convenient.
Data as of 10 Nov 2026, 15:02 UTC
Thin evidence
One scorer or none| CNA (pretix) | CVSS 4.0 | 6.3 |
|---|
- Patch
- Available – fixed in 1.5.4
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade pretix-adyen to 1.5.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| pretixpretix-adyen | Affected
| Fixed in
|
GitHubpretix-adyenpkg:github/pretix-adyenOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, closely monitor payment processing workflows and consider implementing additional validation checks on payment status responses to prevent reuse.
Description
A vulnerability in the payment integration with Adyen allows improper validation of payment status responses. An attacker can reuse a successful payment status from one transaction to fraudulently obtain multiple valid tickets for different payments.