(CVE-2026-118584)
Vulnerability from drupal – Published: 2026-10-28 17:41 – Updated: 2026-10-28 17:41 – Source websiteThe Field Permissions module enables you to set field-level permissions for viewing and editing fields, including a "Private" setting.
The module does not sufficiently restrict access to "Private" fields on entity types that have no field for an author (user account or owner). As a result, a field configured as "Private" on one of these entities can be viewed. Where the entity is editable, the entity can also be edited by anyone who can view it, including anonymous users.
This vulnerability is mitigated by the fact that an administrator must have configured a field as "Private" on an entity type that has no author, and the attacker must already be able to view that entity. Fields set to "Private" on nodes, users, media, comments, and other entity types with an author are not affected. Fields using Custom permissions are not affected.
| URL | Type | |
|---|---|---|
{
"affected": [
{
"database_specific": {
"affected_versions": "\u003c1.6.0"
},
"package": {
"ecosystem": "Packagist:https://packages.drupal.org/8",
"name": "drupal/field_permissions"
},
"ranges": [
{
"database_specific": {
"constraint": "\u003c1.6.0"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1.6.0"
}
],
"type": "ECOSYSTEM"
}
],
"severity": []
}
],
"aliases": [
"CVE-2026-118584"
],
"credits": [
{
"contact": [
"https://www.drupal.org/u/rodrigo-cabo"
],
"name": "Rodrigo Cabo (rodrigo-cabo)"
}
],
"details": "The Field Permissions module enables you to set field-level permissions for viewing and editing fields, including a \"Private\" setting.\n\nThe module does not sufficiently restrict access to \"Private\" fields on entity types that have no field for an author (user account or owner). As a result, a field configured as \"Private\" on one of these entities can be viewed. Where the entity is editable, the entity can also be edited by anyone who can view it, including anonymous users.\n\nThis vulnerability is mitigated by the fact that an administrator must have configured a field as \"Private\" on an entity type that has no author, and the attacker must already be able to view that entity. Fields set to \"Private\" on nodes, users, media, comments, and other entity types with an author are not affected. Fields using *Custom permissions* are not affected.",
"id": "DRUPAL-CONTRIB-2026-289",
"modified": "2026-10-28T17:41:55.000Z",
"published": "2026-10-28T17:41:55.000Z",
"references": [
{
"type": "WEB",
"url": "https://www.drupal.org/sa-contrib-2026-289"
}
],
"schema_version": "1.7.0"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.