Quick answers
- Is CVE-2026-126737 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-126737 being exploited in the wild.
- How severe is CVE-2026-126737?
- Informational severity, published 11 November 2026.
- Which products and versions are affected?
- Mollie for Drupal before 2.3.2; Packagist:Https://Packages.Drupal.Org/8 Drupal/Mollie ECOSYSTEM:introduced=0,fixed=2.3.2.
- Is there a fix for CVE-2026-126737?
- Yes. Packagist:Https://Packages.Drupal.Org/8 Drupal/Mollie: upgrade to 2.3.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-126737 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-126737?
- Check whether you run Mollie for Drupal or Packagist:Https://Packages.Drupal.Org/8 Drupal/Mollie at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Packagist:Https://Packages.Drupal.Org/8 Drupal/Mollie: upgrade to 2.3.2 or later
Technical details
The module fails to sufficiently validate incoming webhook calls from Mollie's payment gateway, allowing an attacker to forge or manipulate webhook data. This is a webhook validation bypass (CWE-347: Improper Verification of Cryptographic Signature). The attack requires network access to send crafted webhook requests and can result in incorrect payment application without proper authorization checks.
Affected products
- Mollie Mollie for Drupal before 2.3.2
Identifiers
- CVE-2026-126737
- DRUPAL-CONTRIB-2026-328
Timeline
- 2026-11-11: disclosed