Is CVE-2026-118555 exploited in the wild?

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

How severe is CVE-2026-118555?

Informational severity, published 30 October 2026.

How is CVE-2026-118555 attacked?

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

Am I affected by CVE-2026-118555?

Check whether you run Drupal Commerce License or Packagist:Https://Packages.Drupal.Org/8 Drupal/Commerce License 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-118555: Drupal Commerce License privilege escalation via access bypass

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

The Commerce License module for Drupal allows organizations to sell licenses that grant access to protected resources like user roles and content. A user with the "update own commerce_license" permission can exploit insufficient field restrictions to modify their own license to grant administrator-level access, achieving privilege escalation. This requires the attacker to already own a license and have been granted this specific permission, which is not given by default.

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

Quick answers

Is CVE-2026-118555 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-118555 being exploited in the wild.
How severe is CVE-2026-118555?: Informational severity, published 30 October 2026.
Which products and versions are affected?: Drupal Commerce License before 3.1.1; Packagist:Https://Packages.Drupal.Org/8 Drupal/Commerce License ECOSYSTEM:introduced=0,fixed=3.1.1.
Is there a fix for CVE-2026-118555?: Yes. Packagist:Https://Packages.Drupal.Org/8 Drupal/Commerce License: upgrade to 3.1.1 or later. Until then: Sites that have granted the "update own commerce_license" permission should review role licenses for unexpected roles and audit which users hold administrative roles to detect unauthorized privilege escalation. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-118555 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-118555?: Check whether you run Drupal Commerce License or Packagist:Https://Packages.Drupal.Org/8 Drupal/Commerce License 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 License: upgrade to 3.1.1 or later

Sites that have granted the "update own commerce_license" permission should review role licenses for unexpected roles and audit which users hold administrative roles to detect unauthorized privilege escalation.

Technical details

The module fails to properly restrict access to license fields for users holding the "update own commerce_license" permission, allowing them to modify the rights and state of their own licenses. An authenticated user with this permission can escalate privileges up to Administrator role by changing license fields. The vulnerability requires the attacker to own a license and hold the specific permission, and no public exploitation has been reported.

Affected products

Drupal Commerce License before 3.1.1

Identifiers

CVE-2026-118555
DRUPAL-CONTRIB-2026-260

Timeline

2026-10-28: disclosed
2026-10-28: advisory: SA-CONTRIB-2026-260 published

References

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