Firebase Php Jwt

Submit a proposal Propose CVE/GCVE/GHSA reference

Approved changes feed: RSS · Atom

cpe:2.3:a:google:firebase_php-jwt:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorGoogle (f181d1eb-7269-5bae-b76e-e66ceb214562)
ProductFirebase Php Jwt (388bbd3f-fa6d-5b23-964c-93eb8ac6aa5e)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:github/firebase/php-jwt purl2cpe 2026-06-01 10:16:38.605933
pkg:github/luciferous/jwt purl2cpe 2026-06-01 10:16:38.605937

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2025-45769 vulnerable 2026-06-08 07:25:11.084564 Details available
php-jwt v6.11.0 was discovered to contain weak encryption. NOTE: this issue has been disputed on the basis that key lengths are expected to be set by an application, not by this library. This dispute is subject to review under CNA rules 4.1.4, 4.1.14, and other rules; the dispute tagging is not meant to recommend an outcome for this CVE Record.
Published: 2025-07-31T00:00:00.000Z
Updated: 2026-02-18T21:34:19.453Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2021-46743 vulnerable 2026-06-08 05:38:03.766103 Details available
In Firebase PHP-JWT before 6.0.0, an algorithm-confusion issue (e.g., RS256 / HS256) exists via the kid (aka Key ID) header, when multiple types of keys are loaded in a key ring. This allows an attacker to forge tokens that validate under the incorrect key. NOTE: this provides a straightforward way to use the PHP-JWT library unsafely, but might not be considered a vulnerability in the library itself.
Published: 2022-03-29T06:40:18.000Z
Updated: 2024-08-04T05:17:41.727Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.