How severe is GHSA-jhmr-57cj-q6g9?

No CVSS score has been assigned to GHSA-jhmr-57cj-q6g9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jhmr-57cj-q6g9?

GHSA-jhmr-57cj-q6g9 affects the following packages: github.com/komari-monitor/komari (Go). Ecosystems affected: Go.

How do I fix GHSA-jhmr-57cj-q6g9?

Update github.com/komari-monitor/komari to 0.0.0-20250809064056-cc3d54bff4c6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jhmr-57cj-q6g9 is resolved across your whole dependency graph.

How do I detect GHSA-jhmr-57cj-q6g9 in my Go dependencies?

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

How do I mitigate GHSA-jhmr-57cj-q6g9 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.

How does O3 Security protect against GHSA-jhmr-57cj-q6g9?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-jhmr-57cj-q6g9 can be triaged on real exposure rather than presence alone.

Is GHSA-jhmr-57cj-q6g9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-jhmr-57cj-q6g9 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-jhmr-57cj-q6g9 published, and has it been updated?

GHSA-jhmr-57cj-q6g9 was published on August 12, 2025 and was last updated on August 18, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

GHSA-jhmr-57cj-q6g9 — komari

Fix: komari-monitor/komari@cc3d54b

GHSA-jhmr-57cj-q6g9 is a security vulnerability in github.com/komari-monitor/komari. A fix is available for github.com/komari-monitor/komari — see the affected versions and patch details below.

Komari vulnerable to 2FA Authentication Bypass

Also known asGO-2025-3873

Published

Aug 12, 2025

Updated

Aug 18, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 18, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/komari-monitor/komari

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

Logic error in 2FA verification condition allows bypass of two-factor authentication

Details

https://github.com/komari-monitor/komari/blob/bd5a6934e1b79a12cf1e6a9bba5372d0e04f3abc/api/login.go#L55

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

Impact

Bypass 2FA Authentication

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/komari-monitor/komari`	all versions	0.0.0-20250809064056-cc3d54bff4c6`go get github.com/komari-monitor/komari@v0.0.0-20250809064056-cc3d54bff4c6`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/komari-monitor/komari, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/komari-monitor/komari to 0.0.0-20250809064056-cc3d54bff4c6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jhmr-57cj-q6g9 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-jhmr-57cj-q6g9 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-jhmr-57cj-q6g9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Logic error in 2FA verification condition allows bypass of two-factor authentication ### Details https://github.com/komari-monitor/komari/blob/bd5a6934e1b79a12cf1e6a9bba5372d0e04f3abc/api/login.go#L55 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 ### Impact Bypass 2FA Authentication

O3 Security · Impact-Aware SCA

Is GHSA-jhmr-57cj-q6g9 in your dependencies?

O3 Security finds GHSA-jhmr-57cj-q6g9 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works