Summary
User enumeration in authentication mechanisms
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.
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
lexik/jwt-authentication-bundle to 2.10.7 or later; lexik/jwt-authentication-bundle to 2.11.3 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-2FRX-J9HJ-6C65? GHSA-2FRX-J9HJ-6C65 is a low-severity security vulnerability in lexik/jwt-authentication-bundle (composer), affecting versions < 2.10.7. It is fixed in 2.10.7, 2.11.3.
- Which versions of lexik/jwt-authentication-bundle are affected by GHSA-2FRX-J9HJ-6C65? lexik/jwt-authentication-bundle (composer) versions < 2.10.7 is affected.
- Is there a fix for GHSA-2FRX-J9HJ-6C65? Yes. GHSA-2FRX-J9HJ-6C65 is fixed in 2.10.7, 2.11.3. Upgrade to this version or later.
- Is GHSA-2FRX-J9HJ-6C65 exploitable, and should I be worried? Whether GHSA-2FRX-J9HJ-6C65 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-2FRX-J9HJ-6C65 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-2FRX-J9HJ-6C65?
- Upgrade
lexik/jwt-authentication-bundleto 2.10.7 or later - Upgrade
lexik/jwt-authentication-bundleto 2.11.3 or later
- Upgrade