CVE-2026-107311: Permissions by term · This module enables you to restrict view access to single nodes via taxonomy terms
Affects drupal/permissions_by_termSource GCVE Database
Not known to be exploited · CVSS 3.7 Low : upgrade to 3.1.41 when convenient.
Data as of 21 Nov 2026, 17:34 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 3.7 |
|---|
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.1.41
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
Upgrade drupal/permissions_by_term to 3.1.41.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Packagist https //packages.drupal.org/8drupal/permissions_by_term | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available for this vulnerability. Users should upgrade to version 3.1.41 or later of the 'Permissions by term' module to remediate the issue. No additional mitigation steps are indicated beyond applying the official fix.
Description
The Drupal module 'Permissions by term' allows restricting view access to nodes based on taxonomy terms. A vulnerability exists where, in 'Permission mode', access rights are not properly checked when a node references a deleted taxonomy term and is accessed via JSON:API. Exploitation requires a specific module configuration, the presence of references to deleted terms, and access through JSON:API. A patch is available for versions prior to 3.1.41.