Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-84917 Overview
CVE-2026-84917 is an Incorrect Authorization vulnerability [CWE-863] in the Drupal Jsonapi Role Access contributed module. The flaw allows forceful browsing, enabling unauthorized users to access JSON:API resources that should be restricted by role-based access controls. The issue affects Jsonapi Role Access versions 0.0.0 through 2.0.2. Site operators relying on this module to gate JSON:API endpoints by role may inadvertently expose protected content, user data, or configuration entities to unauthenticated or lower-privileged requesters.
Critical Impact
Attackers can bypass role-based JSON:API restrictions and retrieve resources intended for privileged users through direct URL manipulation.
Affected Products
- Drupal Jsonapi Role Access module versions 0.0.0 to 2.0.2
- Drupal sites exposing JSON:API endpoints gated by this module
- Any site relying on Jsonapi Role Access for authorization enforcement
Discovery Timeline
- 2026-10-22 - CVE-2026-84917 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-84917
Vulnerability Analysis
The vulnerability resides in how the Jsonapi Role Access module enforces authorization decisions on JSON:API requests. Drupal's JSON:API module exposes entities through predictable REST endpoints such as /jsonapi/node/{bundle} and /jsonapi/user/user. The contributed Jsonapi Role Access module is intended to restrict which roles may access which resources. The module performs its access check incorrectly, allowing requesters to reach protected resources by directly browsing to the endpoint URL. This classifies the issue as a Broken Access Control weakness under CWE-863.
Root Cause
The root cause is an authorization check that does not fully evaluate the requester's roles against the configured resource restrictions. Access logic likely runs on a subset of request paths or returns a permissive decision when a role mapping is undefined. As a result, the enforcement layer fails open rather than denying by default, which contradicts the principle of secure-by-default authorization.
Attack Vector
Exploitation requires only the ability to issue HTTP requests against the target Drupal site. An attacker enumerates JSON:API endpoints and requests resources that the module should block. Because the check is bypassable, the server returns the restricted data. No authentication may be required depending on the resource configuration, and no user interaction is needed. See the Drupal Security Advisory SA-CONTRIB-2026-127 for technical details.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-84917
Indicators of Compromise
- Unexpected GET requests to /jsonapi/* endpoints from unauthenticated sessions or low-privilege accounts.
- Elevated response sizes on JSON:API endpoints that should return 403 for the requesting role.
- Access log entries showing enumeration patterns across multiple /jsonapi/{entity_type}/{bundle} paths.
Detection Strategies
- Review web server and Drupal access logs for successful 2xx responses to JSON:API endpoints from users whose roles should be denied.
- Compare the installed Jsonapi Role Access module version against 2.0.2 and flag any instance at or below that version.
- Correlate anomalous JSON:API traffic volume with the module's presence using data lake queries over normalized web logs.
Monitoring Recommendations
- Instrument the Drupal site to log JSON:API authorization decisions, including the resolved role set and the matched access rule.
- Alert on bursts of JSON:API requests originating from a single IP that touch multiple entity types or bundles.
- Monitor outbound data volumes from the web tier for exfiltration patterns following JSON:API probing.
How to Mitigate CVE-2026-84917
Immediate Actions Required
- Upgrade the Jsonapi Role Access module to a version released after 2.0.2 as published in the Drupal security advisory.
- Audit JSON:API endpoint exposure and confirm that sensitive entity types are not inadvertently published.
- Review access logs for prior exploitation and rotate any credentials or tokens that may have been exposed through protected endpoints.
Patch Information
Refer to the Drupal Security Advisory SA-CONTRIB-2026-127 for the fixed module release and upgrade instructions. Apply the patched version through Composer or the Drupal update workflow and clear caches after deployment.
Workarounds
- Temporarily disable the Jsonapi Role Access module and enforce access through Drupal core permissions or the JSON:API Extras module until patching is complete.
- Restrict /jsonapi/* paths at the reverse proxy or web application firewall to authenticated sessions only.
- Remove or unpublish sensitive entities from JSON:API exposure by configuring entity-level access controls directly in Drupal.
# Composer upgrade example - replace with the fixed version from the advisory
composer update drupal/jsonapi_role_access --with-dependencies
drush updatedb
drush cache:rebuild
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

