Is web-token/jwt-bundle 4.2 vulnerable?

Composer · 8 releases from 4.2.0 to 4.2.7 · latest web-token/jwt-bundle is 4.2.7 · checked 18 Nov 2026

No known advisories in the last release

No. No web-token/jwt-bundle 4.2.x release has a known security advisory.

Is your project on an affected web-token/jwt-bundle?

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

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Which of your client projects are still on web-token/jwt-bundle 4.2?

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

Other web-token/jwt-bundle versions

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