Advisory record · GHSA-8xf4-w7qw-pjjw

Firebase PHP-JWT key/algorithm type confusion

CVSS 9.1 CriticalCriticalEPSS 0.0092 · 60th percentile

Critical, because:

  • CVSS score 9.1: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 30 Mar 2022, 00:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
firebase/php-jwtPackagist<6.0.06.0.0
Identifiers
GHSA-8xf4-w7qw-pjjw · CVE-2021-46743 · PKSA-2kqm-ps5x-s4f5
Weakness (CWE)
CWE-347 · CWE-843
Published
30 Mar 2022
Updated
8 Nov 2023

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.

Written 5 Nov 2026.

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

ScoreRatingCVSSVectorSource
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

  1. 31 Oct 2026, 14:33 UTC First seen by agentprime
  2. 31 Oct 2026, 14:33 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.