Is debug 3.2 vulnerable?

npm · 8 releases from 3.2.0 to 3.2.7 · latest debug is 4.4.3 · checked 2 Nov 2026

No known advisories in the last release

debug 3.2.7, the last 3.2 release, has no known advisories. 1 advisory affects earlier 3.2.x releases, so update to 3.2.7.

Update within 3.2:npm install debug@3.2.7

Is your project affected?

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

Fixed within 3.2.x, affecting earlier releases

  • LowCVE-2017-16137GHSA-gxpj-cx7g-858c9 Aug 2018

    Regular Expression Denial of Service in debug

    Affected
    <2.6.9 · >=3.0.0 <3.1.0 · >=3.2.0 <3.2.7 · >=4.0.0 <4.3.1
    Fixed in
    2.6.9, 3.1.0, 3.2.7, 4.3.1

Which of your client projects are still on debug 3.2?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact debug 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 debug 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.