Is CVE-2026-107311 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-107311 being exploited in the wild.

How severe is CVE-2026-107311?

Informational severity, published 30 October 2026.

Is there a fix for CVE-2026-107311?

Yes. Packagist:Https://Packages.Drupal.Org/8 Drupal/Permissions By Term: upgrade to 3.1.41 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-107311 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-107311?

Check whether you run Drupal Permissions by Term or Packagist:Https://Packages.Drupal.Org/8 Drupal/Permissions By Term 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.

CVE-2026-107311: Drupal Permissions by Term access control bypass in JSON:API

CVE-2026-107311 · Severity: info · Published 2026-10-30

Permissions by Term is a Drupal module that restricts content access based on taxonomy categories. When configured in Permission mode, the module fails to properly validate access rights when content references a deleted taxonomy term accessed through the JSON:API endpoint, potentially exposing restricted content to unauthorized users.

Technologies: Packagist:Https://Packages.Drupal.Org/8 Drupal/Permissions By Term. Vendors: Drupal, Packagist:Https://Packages.Drupal.Org/8.

Quick answers

Is CVE-2026-107311 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-107311 being exploited in the wild.
How severe is CVE-2026-107311?: Informational severity, published 30 October 2026.
Which products and versions are affected?: Drupal Permissions by Term <3.1.41; Packagist:Https://Packages.Drupal.Org/8 Drupal/Permissions By Term ECOSYSTEM:introduced=0,fixed=3.1.41.
Is there a fix for CVE-2026-107311?: Yes. Packagist:Https://Packages.Drupal.Org/8 Drupal/Permissions By Term: upgrade to 3.1.41 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-107311 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-107311?: Check whether you run Drupal Permissions by Term or Packagist:Https://Packages.Drupal.Org/8 Drupal/Permissions By Term 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/Permissions By Term: upgrade to 3.1.41 or later

Technical details

The module insufficiently validates access rights in Permission mode when a node containing a reference to a deleted taxonomy term is accessed via JSON:API. This is an information disclosure vulnerability requiring specific preconditions: Permission mode configuration, a deleted term reference, and JSON:API access. A fix is available in version 3.1.41.

Affected products

Drupal Permissions by Term <3.1.41

Identifiers

CVE-2026-107311
DRUPAL-CONTRIB-2026-214

Timeline

2026-10-07: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.