Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Firebase PHP-JWT versions before 6.0.0 are affected by an algorithm-confusion issue (such as RS256 versus HS256) involving the kid header when multiple types of keys are loaded in a key ring. An attacker who can submit tokens to the application could forge tokens that validate under the wrong key. Upgrade firebase/php-jwt to 6.0.0 or later. The source notes that this may reflect unsafe use of the library rather than a flaw in the library itself.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 9.1 | Critical | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS 0.0092, the 60th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:33 UTC First seen by agentprime
- 31 Oct 2026, 14:33 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-8xf4-w7qw-pjjw
- OSV: GHSA-8xf4-w7qw-pjjw
- nvd.nist.gov/vuln/detail/CVE-2021-46743
- github.com/firebase/php-jwt/issues/351
- github.com/FriendsOfPHP/security-advisories/blob/master/firebase/php-jwt/CVE-2021-46743.yaml
- github.com/firebase/php-jwt
- github.com/firebase/php-jwt/releases/tag/v6.0.0