CVE-2026-106550: Mozilla Node-convict · ‘Prototype Pollution’
Affects Mozilla Node-convictSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 20 Nov 2026, 17:34 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 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 24 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MozillaNode-convict | Affected
| Fixed in– |
npmnode-convictpkg:npm/node-convictOther threats | 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
Until a patch is available, avoid forwarding attacker-controlled keys into config.set() or implement additional input validation to prevent prototype pollution attacks.
Description
Mozilla's Node-convict version 6.2.2 is affected by a prototype pollution vulnerability in the config.set() function. This flaw allows an attacker who can control configuration keys to overwrite core JavaScript methods such as Object.assign by writing arbitrary properties to constructor.<key>. The vulnerability bypasses existing filters and can cause persistent process-wide failures, resulting in denial of service that requires a restart. Exploitation requires an endpoint that forwards attacker-controlled keys into config.set().