CVE-2026-119038
Low risk· EPSS 6%Exploitation Probability (EPSS)
Low risk6th percentile - higher than 6% of all known CVEs
Summary
Business::GoCardless versions before 1.01 for Perl complete redirect flows without checking the session token, letting a leaked redirect flow ID create payments against another customer's mandate. confirm_resource takes no session token from the caller and always accepts the flow, and since version 1.00 a flow with a mandate is returned as confirmed without being completed again.
Risk Assessment
A remote attacker who obtains another customer's redirect flow ID can create payments or subscriptions against that customer's mandate.
Recommendation
Update Business::GoCardless to version 1.01 or later.
Other vulnerabilities in Business::GoCardless
See all- CVE-2026-119037Low risk· EPSS 2%
Business::GoCardless versions before 1.01 for Perl accept forged webhooks when a configured webhook secret is undef or empty. signature_valid uses each configured secret as the HMAC key, and Digest::SHA treats undef and an empty string as an empty key.
- CVE-2026-119036Low risk· EPSS 7%
Business::GoCardless versions before 1.01 for Perl allow memory exhaustion by flattening legacy webhook payloads before checking their signature. A payload with a top-level "payload" key is flattened into key-value pairs, where a long key holding a long array costs memory proportional to the key length times the array length.
Original NVD description (English source)
Business::GoCardless versions before 1.01 for Perl complete redirect flows without checking the session token, letting a leaked redirect flow ID create payments against another customer's mandate. confirm_resource takes no session token from the caller. It reads the redirect flow back from the GoCardless API and completes it with the token from that response, so the check that the flow is completed by the session that started it always passes. It then creates the requested payment or subscription against the flow's mandate. Since version 1.00, a flow that already has a mandate is returned as confirmed without being completed again, so the same ID creates a new payment on every call. A remote attacker who obtains another customer's redirect flow ID can create payments or subscriptions against that customer's mandate.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS

