Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Kimai versions before 2.54.0 (kimai/kimai on Packagist) leak whether a username exists through response timing in the API token authenticator, because a missing user skips the password hash check and returns about 25 ms faster. An unauthenticated attacker who can reach the API can repeatedly probe usernames via the legacy X-AUTH-USER header, which is accepted by default in 2.x and has no login throttling. The source notes the response body and status are identical and the impact is limited, and it says to upgrade to 2.54.0, which is the fixed version.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 6.3 | Medium | 4.0 | CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N | CNA (VulnCheck) |
- CISA KEV Not listed.
- EPSS 0.0031, the 23rd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:07 UTC First seen by agentprime
- 31 Oct 2026, 14:07 UTC Confirmed by OSV