Quick answers
- Is CVE-2026-96385 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-96385 being exploited in the wild.
- How severe is CVE-2026-96385?
- Informational severity, published 22 October 2026.
- Which products and versions are affected?
- Drupal REST & JSON API Authentication before 3.2.0; Packagist:Https://Packages.Drupal.Org/8 Drupal/Rest Api Authentication ECOSYSTEM:introduced=0,fixed=3.2.0.
- Is there a fix for CVE-2026-96385?
- Yes. Packagist:Https://Packages.Drupal.Org/8 Drupal/Rest Api Authentication: upgrade to 3.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-96385 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-96385?
- Check whether you run Drupal REST & JSON API Authentication or Packagist:Https://Packages.Drupal.Org/8 Drupal/Rest Api Authentication at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Packagist:Https://Packages.Drupal.Org/8 Drupal/Rest Api Authentication: upgrade to 3.2.0 or later
Technical details
The module contains an access bypass vulnerability due to insufficient validation of authentication requirements across all API request paths. The vulnerability allows unauthenticated or improperly authenticated requests to reach protected API endpoints. A fix is available in version 3.2.0 and later.
Affected products
- Drupal REST & JSON API Authentication before 3.2.0
Identifiers
- CVE-2026-96385
- DRUPAL-CONTRIB-2026-182
Timeline
- 2026-09-23: disclosed