Is terser 0.0 vulnerable?

npm · 1 release from 0.0.1 to 0.0.1 · latest terser is 5.51.2 · checked 2 Nov 2026

Yes: 1 known advisory

Yes. terser 0.0.1, the last 0.0 release, is affected by 1 known security advisory (1 high), including CVE-2022-25858. Upgrade to 4.8.1 or later to fix all of them.

Upgrade with:npm install terser@4.8.1

Is your project affected?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Advisories affecting terser 0.0.1

  • HighCVE-2022-25858GHSA-4wf5-vphf-c2xc16 Jul 2022

    Terser insecure use of regular expressions leads to ReDoS

    Affected
    <4.8.1 · >=5.0.0 <5.14.2
    Fixed in
    4.8.1, 5.14.2

Which of your client projects are still on terser 0.0?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact terser version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

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

Other terser versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the npm registry. Refreshed daily.