CVE-2026-126745: Realname · This module enables you to display users by a configurable "real name" pattern built from
Affects drupal/realnameSource GCVE Database
Not known to be exploited : upgrade to 2.0.1 soon.
Data as of 11 Nov 2026, 20:03 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- Patch
- Available – fixed in 2.0.1
Exploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 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 11 Nov 2026.
What to do
Upgrade drupal/realname to 2.0.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Packagist https //packages.drupal.org/8drupal/realname | 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
Upgrade the Drupal Realname module to version 2.0.1 or later, where this vulnerability is fixed. Ensure that real name patterns do not include unsanitized user-supplied data. No other mitigation is required if the patch is applied.
Description
The Drupal Realname module allows displaying user names based on configurable patterns using tokens. A vulnerability exists where user input used in these patterns is not properly sanitized, enabling an attacker to inject and have Twig syntax evaluated when their name is displayed. Exploitation requires the site to be configured with a real name pattern that includes user-supplied data and the attacker to have the ability to edit their own profile data. This issue is fixed in version 2.0.1 of the module.