Skip to main content
VulnerabilityPublished

CVE-2026-122077: drupal/allowed_languages · The Allowed Languages module makes it possible to set restrictions on which content a user can edit

Affects drupal/allowed_languagesSource GCVE Database

0
Compare

Not known to be exploited : upgrade to 2.0.3 when convenient.

Data as of 4 Nov 2026, 21:07 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Patch
Available – fixed in 2.0.3

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 4 Nov 2026.

What to do

Upgrade drupal/allowed_languages to 2.0.3.

Affected software

ProductAffectedFixed in
Packagist https //packages.drupal.org/8drupal/allowed_languagesAffected
  • <2.0.3
Fixed in
  • 2.0.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fixed version 2.0.3 of the Allowed Languages module is available and should be applied to remediate this vulnerability. Users should upgrade to version 2.0.3 or later to ensure proper enforcement of language restrictions during content creation.

Description

The Allowed Languages module for Drupal allows setting restrictions on which content a user can edit based on language. However, it does not sufficiently prevent users from creating content in disallowed languages if they have permission to create content in at least one language. This vulnerability affects versions prior to 2.0.3 and has been fixed in version 2.0.3.

References

Community reviews

Loading reviews…