CVE-2026-3210: Drupal Material Icons · Incorrect Authorization
Affects Drupal Material IconsSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.0.4 when convenient.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.0.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 29 Oct 2026.
What to do
Upgrade Material Icons and drupal/material_icons to 2.0.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| DrupalMaterial Icons | Affected
| Fixed in
|
Packagistdrupal/material_iconspkg:composer/drupal/material_iconsOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2026-3210, organizations should immediately identify Drupal installations using the Material Icons module and verify the version in use. Upgrading the module to version 2.0.4 or later, once released, is the most effective remediation. If you cannot patch yet, organizations should restrict access to the affected module's resources by implementing strict web server access controls or Drupal permission configurations to prevent unauthorized browsing. Conduct thorough audits of user roles and permissions to ensure least privilege principles are enforced. Employ web application firewalls (WAFs) to detect and block suspicious forceful browsing attempts targeting the module's endpoints. Additionally, implement comprehensive logging and alerting to detect anomalous access patterns indicative of exploitation attempts. Regularly review and update Drupal core and contributed modules to minimize exposure to known vulnerabilities. Consider isolating critical Drupal instances behind VPNs or IP whitelisting where feasible to reduce attack surface.
Description
Incorrect Authorization vulnerability in Drupal Material Icons allows Forceful Browsing.This issue affects Material Icons: from 0.0.0 before 2.0.4.