Skip to main content
VulnerabilityPublished

CVE-2026-118556: Commerce shipping · This module enables you to sell tangible products via Drupal Commerce that are

Affects drupal/commerce_shippingSource GCVE Database

0

Not known to be exploited : upgrade to 3.0.6 or 2.16.0 soon.

Data as of 28 Oct 2026, 20:44 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Patch
Available – fixed in 3.0.6, 2.16.0

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade drupal/commerce_shipping to 3.0.6 or 2.16.0.

Affected software

ProductAffectedFixed in
Packagist https //packages.drupal.org/8drupal/commerce_shippingAffected
  • <2.16.0
  • >=3.0.0 <3.0.6
Fixed in
  • 2.16.0
  • 3.0.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the official patches by upgrading to Drupal Commerce Shipping versions 2.16.0 or 3.0.6 or later. Since a patch is available, remediation should be performed promptly to prevent unauthorized shipment manipulation.

Description

The Drupal Commerce Shipping module has an access bypass vulnerability that allows insufficient protection of shipment references and shipment entity fields. This flaw can lead to unauthorized modification of shipment states or deletion of shipments. Exploitation requires the attacker to have a cart with API-based access, which mitigates the risk to some extent. Fixed versions 2.16.0 and 3.0.6 address this issue.

References

Community reviews

Loading reviews…