Is web-token/jwt-bundle 4.0 vulnerable?
Composer · 10 releases from 4.0.0 to 4.0.9 · latest web-token/jwt-bundle is 4.2.7 · checked 18 Nov 2026
No known advisories in the last release
web-token/jwt-bundle 4.0.9, the last 4.0 release, has no known advisories. 1 advisory affects earlier 4.0.x releases, so update to 4.0.9.
composer require web-token/jwt-bundle:^4.0.9Is your project on an affected web-token/jwt-bundle?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 4.0.x, affecting earlier releases
PHP JWT Framework: JWSVerifier uses algorithm from unprotected header, enabling algorithm confusion attacks
- Affected
- <3.4.10 · >=4.0.0 <4.0.7 · >=4.1.0 <4.1.7
- Fixed in
- 3.4.10, 4.0.7, 4.1.7
Every web-token/jwt-bundle 4.0.x release
Affected: 4.0.0 to 4.0.6. 4.0.7 and later are not affected. Latest web-token/jwt-bundle: 4.2.7.
| Version | Known advisories |
|---|---|
| web-token/jwt-bundle 4.0.9 | None |
| web-token/jwt-bundle 4.0.8 | None |
| web-token/jwt-bundle 4.0.7 | None |
| web-token/jwt-bundle 4.0.6 | GHSA-jc38-x7x8-2xc8 |
| web-token/jwt-bundle 4.0.5 | GHSA-jc38-x7x8-2xc8 |
| web-token/jwt-bundle 4.0.4 | GHSA-jc38-x7x8-2xc8 |
| web-token/jwt-bundle 4.0.3 | GHSA-jc38-x7x8-2xc8 |
| web-token/jwt-bundle 4.0.2 | GHSA-jc38-x7x8-2xc8 |
| web-token/jwt-bundle 4.0.1 | GHSA-jc38-x7x8-2xc8 |
| web-token/jwt-bundle 4.0.0 | GHSA-jc38-x7x8-2xc8 |
Which of your client projects are still on web-token/jwt-bundle 4.0?
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.