CVE-2026-118584: drupal/field_permissions · The Field Permissions module enables you to set field-level permissions for viewing and editing
Affects drupal/field_permissionsSource GCVE Database
Not known to be exploited : upgrade to 1.6.0 soon.
Data as of 28 Oct 2026, 20:30 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- Patch
- Available – fixed in 1.6.0
Exploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade drupal/field_permissions to 1.6.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Packagist https //packages.drupal.org/8drupal/field_permissions | 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
Upgrade the Field Permissions module to version 1.6.0 or later, where this vulnerability is fixed. No other mitigation is required as the vulnerability depends on specific configuration and existing view access.
Description
The Field Permissions module for Drupal allows setting field-level permissions including a "Private" setting. A vulnerability exists where "Private" fields on entity types without an author field are not properly restricted, allowing these fields to be viewed and edited by anyone who can view the entity, including anonymous users. This issue requires that an administrator has configured such a field as "Private" on an authorless entity type and that the attacker can already view the entity. Fields on entities with authors and those using custom permissions are not affected. The vulnerability is fixed in version 1.6.0 of the module.