Summary
generator-jhipster vulnerable to login check Regular Expression Denial of Service
Workarounds
If you have created an application from the master branch, you need to adapt the LOGIN_REGEX in Constants.java. If your regex is
^[a-zA-Z0-9!#$&'*+=?^_`{|}~.-]+@?[a-zA-Z0-9-]+(?:\\.[a-zA-Z0-9-]+)*$
you need to change it too
^(?>[a-zA-Z0-9!$&*+=?^_`{|}~.-]+@[a-zA-Z0-9-]+(?:\\.[a-zA-Z0-9-]+)*)|(?>[_.@A-Za-z0-9-]+)$
If you still have ^[_.@A-Za-z0-9-]*$ there is no need to change it, except you would like to support login with + sign (e.g. [email protected]).
References
Impact
For applications using JWT or session-based authentication (not OIDC), users can input a login string which can cause a denial of service, as parsing it will be too complex.
Here is an example: https://gist.github.com/atomfrede/311f8a9c6eb74c5c5226af0481155207
The vulnerable expression was never officially released. So only when you generated an application from the master branch between 6.8.0 and 6.9.0 your generated application may be vulnerable.
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
If you only used official releases you don't need to patch your application.
Frequently Asked Questions
- What is GHSA-8W7W-67MW-R5P7? GHSA-8W7W-67MW-R5P7 is a high-severity security vulnerability in generator-jhipster (npm), affecting versions > 6.8.0, < 6.9.0. No fixed version is listed yet.
- Which versions of generator-jhipster are affected by GHSA-8W7W-67MW-R5P7? generator-jhipster (npm) versions > 6.8.0, < 6.9.0 is affected.
- Is there a fix for GHSA-8W7W-67MW-R5P7? No fixed version is listed for GHSA-8W7W-67MW-R5P7 yet. Monitor the advisory for updates and apply mitigations in the interim.
- Is GHSA-8W7W-67MW-R5P7 exploitable, and should I be worried? Whether GHSA-8W7W-67MW-R5P7 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-8W7W-67MW-R5P7 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.