Skip to main content

Node View Permissions CVE-2026-8491

| EUVDEUVD-2026-30991 LOW
Improper Check for Unusual or Exceptional Conditions (CWE-754)
2026-05-19 drupal GHSA-xrm3-543w-4g3q
3.7
CVSS 3.1 · NVD

Severity by source

NVD PRIMARY
3.7 LOW
AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Lifecycle Timeline

4
Analysis Generated
May 20, 2026 - 18:25 vuln.today
CVSS changed
May 20, 2026 - 18:22 NVD
3.7 (LOW)
Patch available
May 19, 2026 - 23:02 EUVD
CVE Published
May 19, 2026 - 22:28 nvd
UNKNOWN (no severity yet)

DescriptionCVE.org

Improper Check for Unusual or Exceptional Conditions vulnerability in Drupal Node View Permissions allows Forceful Browsing.

This issue affects Node View Permissions: from 0.0.0 before 1.7.0, from 2.0.0 before 2.0.1.

AnalysisAI

Forceful browsing in the Drupal Node View Permissions module exposes restricted node content to unauthenticated network attackers under high-complexity conditions. Affected are all installations running versions 0.0.0-1.7.0 (branch 1.x) and 2.0.0-2.0.1 (branch 2.x) of the module. The vulnerability is classified as information disclosure only - no integrity or availability impact - and carries a CVSS 3.7 (Low) score; no public exploit code exists and no confirmed active exploitation has been reported (not in CISA KEV), with EPSS placing exploitation probability at 0.01%.

Technical ContextAI

The Node View Permissions module (cpe:2.3:a:drupal:node_view_permissions) extends Drupal's content access control by restricting which roles can view specific nodes. CWE-754 (Improper Check for Unusual or Exceptional Conditions) indicates the root cause is a logic gap: the module fails to correctly handle edge-case or exceptional states during permission evaluation, leaving certain code paths unchecked. This maps to a forceful browsing weakness - an attacker can directly request node URLs and receive content that access control rules should have blocked, because the exceptional condition that should trigger a deny is not caught. The flaw exists across two independent version branches (1.x and 2.x), suggesting the logic error is present in shared permission-checking code rather than a branch-specific change.

RemediationAI

Sites running the 1.x branch should upgrade to Node View Permissions 1.7.0; sites running the 2.x branch should upgrade to 2.0.1. Both patched versions are confirmed available per the Drupal security advisory at https://www.drupal.org/sa-contrib-2026-034. Upgrading via Composer (composer update drupal/node_view_permissions) is the recommended approach on modern Drupal installations. If an immediate upgrade is not feasible, a compensating control is to disable the Node View Permissions module entirely and rely on Drupal core's built-in content access controls - note this trade-off removes the granular per-node view restrictions the module provides. Given the low CVSS score and high attack complexity, this vulnerability can be addressed within a normal patch maintenance window rather than requiring emergency remediation.

Share

CVE-2026-8491 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy