Skip to main content
VulnerabilityPublished

CVE-2026-118567: Bulk update user roles · This module provides a bulk form for assigning or removing roles on multiple

Affects drupal/bulk_update_user_rolesSource GCVE Database

0

Not known to be exploited : upgrade to 1.0.5 when convenient.

Data as of 28 Oct 2026, 20:31 UTC

Severity
Low

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

Patch
Available – fixed in 1.0.5

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/bulk_update_user_roles to 1.0.5.

Affected software

ProductAffectedFixed in
Packagist https //packages.drupal.org/8drupal/bulk_update_user_rolesAffected
  • <1.0.5
Fixed in
  • 1.0.5

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

AI-suggested

Upgrade the 'bulk_update_user_roles' module to version 1.0.5 or later, where the access control issue is fixed. Since a patch is available, applying this official fix is the recommended remediation.

Description

The Drupal module 'bulk_update_user_roles' has a vulnerability that allows unauthorized users to access the bulk role assignment form. This form does not restrict access properly, potentially enabling users without the correct permissions to assign or remove roles on multiple user accounts. However, exploitation requires the attacker to already have the 'administer users' permission, which limits the risk. The issue is fixed in version 1.0.5.

References

Community reviews

Loading reviews…