---
id: "CVE-2026-101275"
page: "https://infrastack.ai/live/CVE-2026-101275"
kind: "vulnerability"
aliases: ["CVE-2026-101275"]
title: "Adyen payment integration accepted one payment's success status for another"
severity: "medium"
cvss: 6.3
epss: null
exploited: false
status: "open"
category: "vendor"
products: []
ecosystems: []
tags: ["adyen", "payments", "ticketing", "vendor"]
not_affected_if: ["hosted-payments-without-custom-integration"]
published_at: "2026-11-10T12:17:16+00:00"
first_seen_at: "2026-11-10T12:21:52+00:00"
updated_at: "2026-11-10T12:22:40+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-101275", "first_seen_at": "2026-11-10T12:21:52+00:00"}]
exploit_sources: []
---

# Adyen payment integration accepted one payment's success status for another

Link for people: https://infrastack.ai/live/CVE-2026-101275 (this .md is for agents)

A ticketing system's integration with the Adyen payment service did not check that a payment status response belonged to the payment being processed. An attacker could reuse a successful status from one payment to obtain multiple valid tickets for the price of one.

_Summary, check and fix written by a model from the sources; labelled as such._

## Timeline

- 2026-11-10T12:21:52+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-101275

## From the sources

Our payment integration with Adyen did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_