1-minute read
What a defender needs to know
Promzard 4.0.0 and earlier insert ctx property names into a JavaScript function’s parameter list, then evaluate the resulting source with vm.runInThisContext(). CERT/CC’s November 12 advisory identifies this as CVE-2026-127109: an attacker who controls a property name through configuration, request input or environment data can execute code with the Node.js process’s privileges. The CVE record says the template itself can be trusted; the risk sits in the context key names.
Find deployed promzard copies in dependency trees and lockfiles, then trace every caller that builds ctx. Follow the names of keys back to their source, especially generic object spreads and parsers that preserve arbitrary input fields. Build the context from expected names and reject unknown names before the library call. Test each exposed route with an unexpected inert field name: the caller should reject it before ctx is built. Where untrusted key names previously reached the library, review process execution and input history; CERT/CC provides no malicious-key signature. npm’s captured latest release is still 4.0.0, so maintain the restriction while assessing a later authoritative fix.