Pug allows JavaScript code execution if an application accepts untrusted inputGHSA-3965-hpx2-q597
MEDIUMFix: pugjs/pug#3428GHSA-3965-hpx2-q597 is a medium-severity (CVSS 6.8) Code Injection vulnerability in pug-code-gen. A fix is available for pug-code-gen — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for GHSA-3965-hpx2-q597.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
pug-code-gennpmpugnpmDescription
Pug through 3.0.2 allows JavaScript code execution if an application accepts untrusted input for the name option of the compileClient, compileFileClient, or compileClientWithDependenciesTracked function. NOTE: these functions are for compiling Pug templates into JavaScript, and there would typically be no reason to allow untrusted callers.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | pug-code-gen | all versions | 3.0.3npm install pug-code-gen@3.0.3 |
| 📦npm | pug | all versions | 3.0.3npm install pug@3.0.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pug-code-gen, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pug-code-gen to 3.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3965-hpx2-q597 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is GHSA-3965-hpx2-q597 in your dependencies?
Find it across npm, including transitive dependencies.