CVE-2026-122073: drupal/name · The Name Field module provides a field for storing a personal name as separate components
Affects drupal/nameSource GCVE Database
Not known to be exploited : upgrade to 1.6.0 soon.
Data as of 4 Nov 2026, 21:07 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- Patch
- Available – fixed in 1.6.0
Exploitation evidence
Disclosed: evidence found.
CVE published 4 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 4 Nov 2026.
What to do
Upgrade drupal/name to 1.6.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Packagist https //packages.drupal.org/8drupal/name | 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 to version 1.6.0 or later of the Name Field module, where the vulnerability has been fixed. Applying this official fix will remediate the issue.
Description
The Name Field module for Drupal allows storing personal names as separate components. A vulnerability exists due to insufficient sanitization of input values, which can cause stored names to be interpreted as HTML. This leads to a cross-site scripting (XSS) vulnerability. The issue affects versions prior to 1.6.0 and has been fixed in version 1.6.0.