CVE-2026-127109VulnerabilityPublished 12 Nov 2026

VU#685399: PromZard context key code injection leads to remote code execution

Source CERT/CC

Compare

Not known to be exploited.

Data as of 12 Nov 2026, 15:19 UTC

Severity

High

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

Exploitation evidence

Disclosed: evidence found.
Public on cve.org; its publication date is not in this record
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 12 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Users should ensure that any data used to populate the ctx object is strictly validated and sanitized. Arbitrary or untrusted keys must not be passed to the ctx object to prevent code injection.

Description

The npm library promzard versions 4.0.0 and earlier contains a vulnerability that allows remote code execution. This occurs because the library directly interpolates keys from a context object into JavaScript code without sanitization, enabling injection of arbitrary code. An attacker who can control these keys can execute code within the Node.js process running promzard. No official fix or vendor coordination is available; users are advised to strictly validate any data used to populate the context object and avoid passing untrusted keys.

Impact

An attacker able to control the keys of the ctx object can inject arbitrary JavaScript code that executes within the Node.js process context. This results in remote code execution, potentially compromising the host running promzard.

Summary

Promzard is a Node.js library for automating configuration workflows by evaluating template modules with a context object (ctx). Versions 4.0.0 and earlier are vulnerable because the keys of the ctx object are directly interpolated as raw JavaScript source code into the parameter list of a function-expression string. This string is then evaluated using vm.runInThisContext(), allowing attacker-controlled JavaScript syntax in keys to be executed. This leads to remote code execution if an attacker can influence the ctx keys, such as through configuration files, HTTP requests, or environment variables.

References

kb.cert.org/vuls/id/685399 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 12 Nov 2026, 15:19 UTC

Technical details

References

Community reviews

Related threats