MediumGHSA-p493-635q-r6grCVE-2021-21353

Remote code execution via the `pretty` option.

Published 3 Mar 2021 · Updated 10 Sept 2026

Affected packages

pugnpm

Affected: <3.0.1
Fixed in: 3.0.1

Update to the fixed version for your release line, for example:npm install pug@3.0.1

pug-code-gennpm

Affected: <2.0.3
Fixed in: 2.0.3

Update to the fixed version for your release line, for example:npm install pug-code-gen@2.0.3

pug-code-gennpm

Affected: >=3.0.0 <3.0.2
Fixed in: 3.0.2

Update to the fixed version for your release line, for example:npm install pug-code-gen@3.0.2

Details

Impact

If a remote attacker was able to control the pretty option of the pug compiler, e.g. if you spread a user provided object such as the query parameters of a request into the pug template inputs, it was possible for them to achieve remote code execution on the node.js backend.

Patches

Upgrade to pug@3.0.1 or pug-code-gen@3.0.2 or pug-code-gen@2.0.3, which correctly sanitise the parameter.

Workarounds

If there is no way for un-trusted input to be passed to pug as the pretty option, e.g. if you compile templates in advance before applying user input to them, you do not need to upgrade.

References

Original report: https://github.com/pugjs/pug/issues/3312

For more information

If you believe you have found other vulnerabilities, please DO NOT open an issue. Instead, you can follow the instructions in our Security Policy

Is GHSA-p493-635q-r6gr in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected pug, and gives you the command that fixes it.

Scan a project free, no signup Or connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.