Is web-token/jwt-bundle 2.2 vulnerable?
Composer · 12 releases from 2.2.0 to 2.2.11 · latest web-token/jwt-bundle is 4.2.7 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. web-token/jwt-bundle 2.2.11, the last 2.2 release, is affected by 1 known security advisory (1 high). Upgrade to 3.4.10 or later to fix all of them.
composer require web-token/jwt-bundle:^3.4.10Is 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
Advisories affecting web-token/jwt-bundle 2.2.11
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 2.2.x release
Affected: 2.2.0 to 2.2.11. Latest web-token/jwt-bundle: 4.2.7.
| Version | Known advisories |
|---|---|
| web-token/jwt-bundle 2.2.11 | GHSA-jc38-x7x8-2xc8 |
| web-token/jwt-bundle 2.2.10 | GHSA-jc38-x7x8-2xc8 |
| web-token/jwt-bundle 2.2.9 | GHSA-jc38-x7x8-2xc8 |
| web-token/jwt-bundle 2.2.8 | GHSA-jc38-x7x8-2xc8 |
| web-token/jwt-bundle 2.2.7 | GHSA-jc38-x7x8-2xc8 |
| web-token/jwt-bundle 2.2.6 | GHSA-jc38-x7x8-2xc8 |
| web-token/jwt-bundle 2.2.5 | GHSA-jc38-x7x8-2xc8 |
| web-token/jwt-bundle 2.2.4 | GHSA-jc38-x7x8-2xc8 |
| web-token/jwt-bundle 2.2.3 | GHSA-jc38-x7x8-2xc8 |
| web-token/jwt-bundle 2.2.2 | GHSA-jc38-x7x8-2xc8 |
| web-token/jwt-bundle 2.2.1 | GHSA-jc38-x7x8-2xc8 |
| web-token/jwt-bundle 2.2.0 | GHSA-jc38-x7x8-2xc8 |
Which of your client projects are still on web-token/jwt-bundle 2.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.