VulnerabilityPublished 12 Nov 2026

CVE-2026-127109: Promzard · Code Injection

Affects PromzardSource CVE Database V5

Compare

Not known to be exploited.

Data as of 12 Nov 2026, 15:47 UTC

Severity

High

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

Thin evidence

One scorer or none

Exploitation evidence

Disclosed: evidence found.
CVE published 12 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 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

Affected software

Product	Affected	Fixed in
PromzardPromzard	Affected <=4.0.0	Fixed in–

AI-suggested

Users should monitor the vendor's advisories for updates. Until a fix is available, avoid using untrusted input to control property names in the context object passed to Promzard templates. Consider isolating the Node.js process or applying runtime restrictions to limit potential damage from code injection.

Description

CVE-2026-127109 is a code injection vulnerability in Promzard's template-loading functionality. It allows an attacker who can control property names in the context object to execute arbitrary code with the privileges of the Node.js process. This occurs because the library inserts context property names into a generated function's parameter list without validation or escaping, then evaluates the source using vm.runInThisContext(). Crafted property names can escape the parameter list and inject JavaScript code, even if the template file is trusted.

Reports on CVE-2026-127109

VU#685399: PromZard context key code injection leads to remote code executionCERT/CC2026-11-12

Impact

Successful exploitation allows an attacker to execute arbitrary code with the same privileges as the Node.js process running Promzard. This can lead to full compromise of the application environment, unauthorized access, data manipulation, or further attacks within the host system.

Summary

The vulnerability in Promzard arises from unsafe handling of property names in the context object (ctx) used during template loading. The library dynamically generates a function whose parameter list includes these property names without sanitization. This function source is then executed in the Node.js environment using vm.runInThisContext(), enabling an attacker controlling property names to inject and execute arbitrary JavaScript code. This flaw is classified as CWE-94 (Code Injection) and affects Promzard versions from 0 up to and including 4.0.0.

CWE-94Improper Control of Generation of Code (Code Injection) (opens in a new tab)
Base weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #10OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
Architecture and Design · Refactoring
Refactor your program so that you do not have to dynamically generate code.
Architecture and Design
Run your code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V5.2.8 (opens in a new tab)
V5.2.5 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Leverage Executable Code in Non-Executable Files (opens in a new tab)
Manipulating User-Controlled Variables (opens in a new tab)
Code Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/npm/promzard (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

Reports on CVE-2026-127109

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

WeaknessesCWE-94

Technical details

References

Community reviews

Related threats