web-token/jwt-bundle vulnerabilities

JWT Bundle of the JWT Framework.

Registry
Composer
Latest
4.2.7
License
MIT

1 known advisory

The latest version, 4.2.7, is not affected by any of them. Projects on older versions may be.

Update to the latest version:composer require web-token/jwt-bundle:^4.2.7

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

Security advisories for web-token/jwt-bundle

  • HighGHSA-jc38-x7x8-2xc818 Jun 2026

    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

Is your web-token/jwt-bundle version vulnerable?

Which of your client projects still run an old web-token/jwt-bundle?

NPMscan reads the composer.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other Composer packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Composer registry.