Skip to main content
VulnerabilityPublished

CVE-2026-119037: Business-GoCardless (Perl module) · Improper Verification of Cryptographic Signature

Affects Business-GoCardless (Perl module)Source CVE Database V5

0
Compare

Not known to be exploited : upgrade to 1.01 soon.

Data as of 30 Oct 2026, 13:18 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 1.01

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 30 Oct 2026.

What to do

Upgrade Business-GoCardless (Perl module) to 1.01.

Affected software

ProductAffectedFixed in
Business-GoCardlessAffected
  • <1.01
Fixed in
  • 1.01
CPANBusiness-GoCardlesspkg:cpan/Business-GoCardlessOther threatsAffected
  • <1.01
Fixed in
  • 1.01

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Business-GoCardless to version 1.01 or later, where this vulnerability is fixed. The fixed version properly rejects undefined or empty webhook secrets during signature verification, preventing acceptance of forged webhooks.

Description

Business-GoCardless versions before 1.01 for Perl improperly verify cryptographic signatures on webhooks when the configured webhook secret is undefined or empty. This allows an attacker to forge webhooks by signing them with an empty key, which the system accepts as valid. The issue arises because the signature validation function does not reject empty or undefined secrets, which Digest::SHA treats as an empty key.

References

Community reviews

Loading reviews…