Is browserify-sign 4.2 vulnerable?

npm · 7 releases from 4.2.0 to 4.2.6 · latest browserify-sign is 4.2.6 · checked 2 Nov 2026

No known advisories in the last release

browserify-sign 4.2.6, the last 4.2 release, has no known advisories. 1 advisory affects earlier 4.2.x releases, so update to 4.2.6.

Update within 4.2:npm install browserify-sign@4.2.6

Is your project affected?

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

Fixed within 4.2.x, affecting earlier releases

  • HighCVE-2023-46234GHSA-x9w5-v3q2-3rhw26 Oct 2023

    browserify-sign upper bound check issue in `dsaVerify` leads to a signature forgery attack

    Affected
    >=2.6.0 <4.2.2
    Fixed in
    4.2.2

Which of your client projects are still on browserify-sign 4.2?

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