How severe is GHSA-4rr6-gf59-ggw5?

No CVSS score has been assigned to GHSA-4rr6-gf59-ggw5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4rr6-gf59-ggw5?

GHSA-4rr6-gf59-ggw5 affects the following packages: namshi/jose (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-4rr6-gf59-ggw5?

Update namshi/jose to 2.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4rr6-gf59-ggw5 is resolved across your whole dependency graph.

How do I detect GHSA-4rr6-gf59-ggw5 in my Packagist dependencies?

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

How do I mitigate GHSA-4rr6-gf59-ggw5 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.

Is GHSA-4rr6-gf59-ggw5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-4rr6-gf59-ggw5 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-4rr6-gf59-ggw5 published, and has it been updated?

GHSA-4rr6-gf59-ggw5 was published on May 17, 2024 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

namshi/jose - Verification bypass

Real-World Exposure

1 pkg affected

🐘namshi/jose

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	`namshi/jose`	all versions	2.2.0`composer require namshi/jose:^2.2.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for namshi/jose, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update namshi/jose to 2.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4rr6-gf59-ggw5 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.

Frequently Asked Questions

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).

O3 Security · Impact-Aware SCA

Is GHSA-4rr6-gf59-ggw5 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

namshi/jose - Verification bypassGHSA-4rr6-gf59-ggw5