CVE-2026-101275
Received Received - Intake

Payment Status Validation Bypass in Adyen Integration

Vulnerability report for CVE-2026-101275, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-10

Last updated on: 2026-11-10

Assigner: rami.io

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-10
Last Modified
2026-11-10
Generated
2026-11-10
AI Q&A
2026-11-10
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves a flaw in payment integration with Adyen where payment status responses were not properly validated. An attacker could exploit this by using a valid payment status response from one transaction and applying it to another transaction, allowing them to gain access to multiple valid tickets without making additional payments.

Detection Guidance

This vulnerability involves improper validation of payment status responses in Adyen integration. To detect it, review payment logs for duplicate ticket issuances from a single payment. Check for mismatches between payment IDs and ticket IDs in transaction records. Look for multiple successful payments with the same transaction reference.

Impact Analysis

If you are a user of the affected system, this vulnerability could allow attackers to obtain tickets for events or services without paying for them. This could lead to financial losses for the service provider and potentially disrupt legitimate transactions.

Mitigation Strategies

Immediately update the payment integration to strictly validate payment status responses against the correct payment ID. Ensure each payment response is tied to a unique transaction reference. Review and revoke any fraudulently issued tickets. Implement additional logging for payment status checks.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-101275. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...