Skip to main content
VulnerabilityPublished

CVE-2026-1553: Drupal Canvas · Incorrect Authorization

Affects Drupal CanvasSource CVE Database V5

0

Not known to be exploited · CVSS 4.8 Medium : upgrade to 1.0.4 when convenient.

Data as of 26 Oct 2026, 09:16 UTC

CVSS 3.1 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.0.4
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Feb 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 Canvas to 1.0.4.

Affected software

ProductAffectedFixed in
DrupalDrupal CanvasAffected
  • <1.0.4
Fixed in
  • 1.0.4

AI-suggested

1. Upgrade Drupal Canvas to version 1.0.4 or later as soon as the patch is released to address the authorization flaw. 2. Until patching is possible, implement strict access control policies at the web server or application firewall level to restrict access to sensitive URLs or resources associated with Drupal Canvas. 3. Conduct a thorough audit of user permissions and roles within Drupal to ensure least privilege principles are enforced. 4. Monitor web server logs and Drupal access logs for unusual or unauthorized access attempts, especially targeting URLs that may be vulnerable to forceful browsing. 5. Employ web application firewalls (WAFs) with rules designed to detect and block forceful browsing attempts or unauthorized URL access patterns. 6. Educate developers and administrators about secure coding and authorization best practices to prevent similar issues in custom modules or configurations. 7. Regularly review and update security policies and incident response plans to quickly address any exploitation attempts. 8. Consider network segmentation to limit the exposure of Drupal Canvas instances to only trusted internal or external users as appropriate.

Description

Incorrect Authorization vulnerability in Drupal Drupal Canvas allows Forceful Browsing.This issue affects Drupal Canvas: from 0.0.0 before 1.0.4.

References

Community reviews

Loading reviews…