Is CVE-2026-118543 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-118543 being exploited in the wild.

How severe is CVE-2026-118543?

Informational severity, published 30 October 2026.

Which products and versions are affected?

Drupal Commerce versions prior to 2.41.0 and 3.0.0 through 3.3.12; 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-118543?

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-118543 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-118543?

Check whether you run Drupal Commerce 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.

CVE-2026-118543: Drupal Commerce CSRF vulnerability in inbox routes

CVE-2026-118543 · Severity: info · Published 2026-10-30

Drupal Commerce is an e-commerce module that manages shopping carts and checkout for Drupal websites. A missing CSRF token validation in the inbox notification routes allows an attacker to trick administrators into dismissing security update notices by visiting a crafted page. Because the inbox is shared across all administrators, a single compromised admin can hide critical security alerts from the entire team, potentially delaying urgent patching.

Technologies: Drupal Commerce, Packagist:Https://Packages.Drupal.Org/8 Drupal/Commerce. Vendors: Drupal, Packagist:Https://Packages.Drupal.Org/8.

Quick answers

Is CVE-2026-118543 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-118543 being exploited in the wild.
How severe is CVE-2026-118543?: Informational severity, published 30 October 2026.
Which products and versions are affected?: Drupal Commerce versions prior to 2.41.0 and 3.0.0 through 3.3.12; 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-118543?: 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-118543 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-118543?: Check whether you run Drupal Commerce 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

The vulnerability is a cross-site request forgery (CSRF) flaw affecting the Commerce inbox routes that manage notification display. An attacker with network access can craft a malicious page that, when visited by a logged-in user with "access commerce administration pages" permission, silently dismisses messages via state-changing GET or POST requests lacking CSRF token verification. Since the inbox state is shared globally among all administrators, this allows one compromised session to suppress notices for all users, including security update announcements.

Affected products

Drupal Commerce versions prior to 2.41.0 and 3.0.0 through 3.3.12

Identifiers

CVE-2026-118543
DRUPAL-CONTRIB-2026-258

Timeline

2026-10-28: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.