Is jose 3.16 vulnerable?
npm · 2 releases from 3.16.0 to 3.16.1 · latest jose is 6.2.15 · checked 2 Nov 2026
Yes: 2 known advisories
Yes. jose 3.16.1, the last 3.16 release, is affected by 2 known security advisories (2 medium), including CVE-2024-28176, CVE-2022-36083. Upgrade to 4.15.5 or later to fix all of them.
npm install jose@4.15.5Advisories affecting jose 3.16.1
jose vulnerable to resource exhaustion via specifically crafted JWE with compressed plaintext
- Affected
- >=3.0.0 <4.15.5 · <2.0.7
- Fixed in
- 2.0.7, 4.15.5
JOSE vulnerable to resource exhaustion via specifically crafted JWE
- Affected
- >=1.0.0 <1.28.2 · >=2.0.0 <2.0.6 · >=3.0.0 <3.20.4 · >=4.0.0 <4.9.2
- Fixed in
- 1.28.2, 2.0.6, 3.20.4, 4.9.2
Which of your client projects are still on jose 3.16?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact jose version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other jose 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.