How severe is GHSA-2frx-j9hj-6c65?

No CVSS score has been assigned to GHSA-2frx-j9hj-6c65 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2frx-j9hj-6c65?

GHSA-2frx-j9hj-6c65 affects the following packages: lexik/jwt-authentication-bundle (Packagist), lexik/jwt-authentication-bundle (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-2frx-j9hj-6c65?

Update lexik/jwt-authentication-bundle to 2.10.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2frx-j9hj-6c65 is resolved across your whole dependency graph.

How do I detect GHSA-2frx-j9hj-6c65 in my Packagist dependencies?

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

How do I mitigate GHSA-2frx-j9hj-6c65 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-2frx-j9hj-6c65 actively exploited in the wild?

No public exploit code has been indexed for GHSA-2frx-j9hj-6c65 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-2frx-j9hj-6c65 published, and has it been updated?

GHSA-2frx-j9hj-6c65 was published on May 17, 2021 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.

🐘 Packagist

Not in CISA KEV

User enumeration in authentication mechanismsGHSA-2frx-j9hj-6c65

Fix: lexik/LexikJWTAuthenticationBundle@a175d6d

GHSA-2frx-j9hj-6c65 is a security vulnerability in lexik/jwt-authentication-bundle. A fix is available for lexik/jwt-authentication-bundle — see the affected versions and patch details below.

Published

May 17, 2021

Updated

Dec 2, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Dec 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🐘lexik/jwt-authentication-bundle🐘lexik/jwt-authentication-bundle

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

The ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not.

Resolution

We now ensure that a generic message is returned whether the user exists or not if the password is invalid or if the user does not exist.

The patch for this issue is available here for branch 2.10.x and 2.x.

Credits

I would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`lexik/jwt-authentication-bundle`	all versions	2.10.7`composer require lexik/jwt-authentication-bundle:^2.10.7`
🐘Packagist	`lexik/jwt-authentication-bundle`	≥ 2.11.0&&< 2.11.3	2.11.3`composer require lexik/jwt-authentication-bundle:^2.11.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for lexik/jwt-authentication-bundle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update lexik/jwt-authentication-bundle to 2.10.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2frx-j9hj-6c65 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

Description ----------- The ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. Resolution ---------- We now ensure that a generic message is returned whether the user exists or not if the password is invalid or if the user does not exist. The patch for this issue is available [here](https://github.com/lexik/LexikJWTAuthenticationBundle/commit/a175d6dab968d93e96a3e4f80c495435f71d5eb7) for branch 2.10.x and 2.x. Credits ------- I would like to thank James Isaac and Mathias Brodala for repor

O3 Security · Impact-Aware SCA

Is GHSA-2frx-j9hj-6c65 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

User enumeration in authentication mechanismsGHSA-2frx-j9hj-6c65

Real-World Exposure

Description

Description

Resolution

Credits

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-2frx-j9hj-6c65 in your dependencies?