GHSA-2frx-j9hj-6c65
Fix: lexik/LexikJWTAuthenticationBundle@a175d6dGHSA-2frx-j9hj-6c65 is a security vulnerability in lexik/jwt-authentication-bundle. O3 Security confirms whether GHSA-2frx-j9hj-6c65 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
User enumeration in authentication mechanisms
Real-World Exposure
lexik/jwt-authentication-bundle🐘lexik/jwt-authentication-bundleReal-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
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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | lexik/jwt-authentication-bundle | all versions | 2.10.7 |
| 🐘Packagist | lexik/jwt-authentication-bundle | ≥ 2.11.0&&< 2.11.3 | 2.11.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for lexik/jwt-authentication-bundle. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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.
How O3 protects you
O3 pinpoints whether GHSA-2frx-j9hj-6c65 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-2frx-j9hj-6c65. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-2frx-j9hj-6c65 in your dependencies?
O3 detects GHSA-2frx-j9hj-6c65 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.