Quick answers
- Is CVE-2026-126738 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-126738 being exploited in the wild.
- How severe is CVE-2026-126738?
- Informational severity, published 11 November 2026.
- Which products and versions are affected?
- Drupal Mollie 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-126738?
- 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-126738 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-126738?
- Check whether you run Drupal Mollie 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 Mollie for Drupal module improperly handles Mollie API secret tokens, allowing them to be exposed in certain conditions when the mollie_webform submodule is enabled. The vulnerability requires that the vulnerable submodule be active, limiting the attack surface to affected installations. A successful exploit would leak the secret token, granting attackers the ability to perform API operations on behalf of the site.
Affected products
- Drupal Mollie before 2.3.2
Identifiers
- CVE-2026-126738
- DRUPAL-CONTRIB-2026-329
Timeline
- 2026-11-11: disclosed