Quick answers
- Is CVE-2026-127109 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-127109 being exploited in the wild.
- How severe is CVE-2026-127109?
- Informational severity, published 12 November 2026.
- Which products and versions are affected?
- npm promzard.
- Is there a fix for CVE-2026-127109?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-127109 attacked?
- It is attacked over the network or with local access, in a software library.
- Am I affected by CVE-2026-127109?
- Check whether you run promzard (npm). Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in promzard's template-loading functionality, which generates a JavaScript function by inserting context property names directly into a parameter list without validation or escaping, then evaluates the result using vm.runInThisContext(). An attacker who can control property names in the context object can craft a property name that escapes the parameter list syntax and injects malicious JavaScript code. This occurs even when the template file itself is trusted, making the vulnerability a context-manipulation issue.
Affected products
- npm promzard
Timeline
- 2026-11-12: disclosed