CVE-2026-119036

Business::GoCardless versions before 1.01 for Perl allow memory exhaustion by flattening legacy webhook payloads before checking their signature

Published Oct 30, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
Business::GoCardless versions before 1.01 for Perl allow memory exhaustion by flattening legacy webhook payloads before checking their signature.

A webhook body with a top-level "payload" key is verified as a legacy webhook. To rebuild the signed string, the payload is flattened into one key and value pair per leaf, each key carrying the full path to that leaf, and the pairs are then encoded, sorted and joined. A long key holding a long array costs memory proportional to the key length times the array length.

A remote attacker can exhaust memory in the process receiving webhooks with a single request that carries no valid signature.

Analysis

AI-generated

Technical impact

The vulnerability exists when Business::GoCardless flattens the entire payload of a legacy webhook into a long key before verifying its signature. This flattening consumes memory proportional to the key length and the array size, allowing an attacker to submit a single request with an oversized payload that lacks a valid signature, leading to exhaustion of the host process memory and potentially a denial of service.

Affected Systems

All releases of the Business::GoCardless Perl library for the GoCardless API before version 1.01 provided by LEEJO are affected. The flaw impacts any environment that processes incoming webhook payloads using this library.

Risk and Exploitability

An EPSS score of 0.00176 (indicating a very low but non‑zero exploitation probability) and the vulnerability is not listed in the CISA KEV catalog, but memory exhaustion is a high‑impact outcome. The CVSS score of 7.5 indicates a moderate to high severity. A remote attacker who can reach the server’s webhook endpoint can trigger the flaw by sending a single crafted request. Because the library performs signature verification only after payload flattening, no authentication barrier prevents exploitation, making the vulnerability straightforward to use for anyone with network access to the endpoint.

Remediation

Vendor Solution

Upgrade to Business-GoCardless 1.01 or later.


OpenCVE Recommended Actions

  • Upgrade the Business::GoCardless module to version 1.01 or later, which performs signature verification before payload processing.
  • Enforce strict size limits on inbound webhook payloads, rejecting requests that exceed reasonable thresholds to prevent memory exhaustion.
  • Apply request rate limiting and monitoring to detect and mitigate sudden spikes in memory usage during webhook processing.

Generated by OpenCVE AI on November 6, 2026 at 18:13 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Type Values Removed Values Added
First Time appeared Perl
Perl business::gocardless
Vendors & Products Perl
Perl business::gocardless
Type Values Removed Values Added
Description Business::GoCardless versions before 1.01 for Perl allow memory exhaustion by flattening legacy webhook payloads before checking their signature. A webhook body with a top-level "payload" key is verified as a legacy webhook. To rebuild the signed string, the payload is flattened into one key and value pair per leaf, each key carrying the full path to that leaf, and the pairs are then encoded, sorted and joined. A long key holding a long array costs memory proportional to the key length times the array length. A remote attacker can exhaust memory in the process receiving webhooks with a single request that carries no valid signature.
Title Business::GoCardless versions before 1.01 for Perl allow memory exhaustion by flattening legacy webhook payloads before checking their signature
Weaknesses CWE-770
References
Weaknesses
  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
CPANSec
Published
Updated
Nov 6, 2026, 3:52 PM
Reserved
Oct 29, 2026, 11:38 AM
Status
Deferred
Published
Oct 30, 2026, 1:18 PM
Modified
Nov 6, 2026, 4:17 PM