Summary
Komari vulnerable to 2FA Authentication Bypass
Logic error in 2FA verification condition allows bypass of two-factor authentication
Details
There is no way for Verify2Fa to return an error AND true as ok at the same time, any codes are considered as valid.
PoC
Use any 6 digits as 2FA code
Bypass 2FA Authentication
Impact
The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.
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
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-JHMR-57CJ-Q6G9? GHSA-JHMR-57CJ-Q6G9 is a high-severity improper authentication vulnerability in github.com/komari-monitor/komari (go), affecting versions < 0.0.0-20250809064056-cc3d54bff4c6. It is fixed in 0.0.0-20250809064056-cc3d54bff4c6. The application does not adequately verify the identity of a user, device, or process before granting access.
- Which versions of github.com/komari-monitor/komari are affected by GHSA-JHMR-57CJ-Q6G9? github.com/komari-monitor/komari (go) versions < 0.0.0-20250809064056-cc3d54bff4c6 is affected.
- Is there a fix for GHSA-JHMR-57CJ-Q6G9? Yes. GHSA-JHMR-57CJ-Q6G9 is fixed in 0.0.0-20250809064056-cc3d54bff4c6. Upgrade to this version or later.
- Is GHSA-JHMR-57CJ-Q6G9 exploitable, and should I be worried? Whether GHSA-JHMR-57CJ-Q6G9 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-JHMR-57CJ-Q6G9 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-JHMR-57CJ-Q6G9? Upgrade
github.com/komari-monitor/komarito 0.0.0-20250809064056-cc3d54bff4c6 or later.