Quick answers
- Is CVE-2026-118542 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118542 being exploited in the wild.
- How severe is CVE-2026-118542?
- Informational severity, published 30 October 2026.
- Which products and versions are affected?
- Drupal Commerce Core < 2.41.0 or >= 3.0.0 < 3.3.13; Packagist:Https://Packages.Drupal.Org/8 Drupal/Commerce ECOSYSTEM:introduced=0,fixed=2.41.0|ECOSYSTEM:introduced=3.0.0,fixed=3.3.13.
- Is there a fix for CVE-2026-118542?
- Yes. Packagist:Https://Packages.Drupal.Org/8 Drupal/Commerce: upgrade to 2.41.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118542 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-118542?
- Check whether you run Drupal Commerce Core or Packagist:Https://Packages.Drupal.Org/8 Drupal/Commerce 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/Commerce: upgrade to 2.41.0 or later
Technical details
An access bypass vulnerability exists in the store save functionality where insufficient permission checks allow a user with create or edit store permissions to elevate a store to default status without proper authorization. The vulnerability requires the attacker to already possess store-level permissions (either create any store or edit their own store). An authenticated attacker can redirect orders intended for other stores to their own account.
Affected products
- Drupal Commerce Core < 2.41.0 or >= 3.0.0 < 3.3.13
Identifiers
- CVE-2026-118542
- DRUPAL-CONTRIB-2026-257
Timeline
- 2026-10-28: disclosed