How severe is GHSA-h533-5v22-8vcp?

No CVSS score has been assigned to GHSA-h533-5v22-8vcp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-h533-5v22-8vcp?

GHSA-h533-5v22-8vcp affects the following packages: firebase/php-jwt (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-h533-5v22-8vcp?

Update firebase/php-jwt to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h533-5v22-8vcp is resolved across your whole dependency graph.

How do I detect GHSA-h533-5v22-8vcp in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for firebase/php-jwt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-h533-5v22-8vcp if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-h533-5v22-8vcp?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-h533-5v22-8vcp can be triaged on real exposure rather than presence alone.

Is GHSA-h533-5v22-8vcp actively exploited in the wild?

No public exploit code has been indexed for GHSA-h533-5v22-8vcp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-h533-5v22-8vcp published, and has it been updated?

GHSA-h533-5v22-8vcp was published on May 15, 2024 and was last updated on November 29, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

GHSA-h533-5v22-8vcp — firebase/php-jwt

Fix: firebase/php-jwt@b2c2be6

GHSA-h533-5v22-8vcp is a security vulnerability in firebase/php-jwt. A fix is available for firebase/php-jwt — see the affected versions and patch details below.

firebase/php-jwt: "None" Algorithm treated as valid on tokens

Published

May 15, 2024

Updated

Nov 29, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 29, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘firebase/php-jwt

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Several widely-used JSON Web Token (JWT) libraries, including node-jsonwebtoken, pyjwt, namshi/jose, php-jwt, and jsjwt, are affected by critical vulnerabilities that could allow attackers to bypass the verification step when using asymmetric keys (RS256, RS384, RS512, ES256, ES384, ES512).

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`firebase/php-jwt`	all versions	2.0.0`composer require firebase/php-jwt:^2.0.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for firebase/php-jwt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update firebase/php-jwt to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h533-5v22-8vcp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-h533-5v22-8vcp can be triaged on real exposure rather than presence alone.

Tailored to GHSA-h533-5v22-8vcp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-h533-5v22-8vcp in your dependencies?

O3 Security finds GHSA-h533-5v22-8vcp across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works