CVE-2026-80199

LOWPre-NVD 3.73.7—
EchelonGraph scoreMEDIUM confidence

Score 3.7 from GitHub Security Advisory published 2026-08-31. A secondary CVSS source baseline 3.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 3.7Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Kimai before 2.54.0 contains a timing oracle vulnerability in TokenAuthenticator that allows unauthenticated attackers to enumerate valid usernames via X-AUTH-USER header. Attackers can measure response time differences when the password hasher runs only for existing users, enabling username enumeration with no login throttling protection.

CVSS v3
3.7
EG Score
3.7LOWmedium confidence
EG Risk
33
EG Risk 33/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity37% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
21st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 25, 2026

Last Modified

October 8, 2026

References (2)

Vendor Advisories for CVE-2026-80199(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
kimai/kimai0.1 ... 2.9.0 (199 versions)
  • every version up to 2.54.0: fixed in 2.54.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 47× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:13 UTCEPSS rescore
  4. 2026-10-08 16:35 UTCEG score recompute
  5. 2026-10-08 16:35 UTCGHSA enrichment
  6. 2026-10-08 15:41 UTCEG score recompute
  7. 2026-10-08 15:41 UTCGHSA enrichment
  8. 2026-10-07 23:48 UTCEPSS rescore
  9. 2026-10-06 20:45 UTCEG score recompute
  10. 2026-10-06 20:45 UTCGHSA enrichment
  11. 2026-10-06 15:18 UTCEPSS rescore
  12. 2026-10-05 17:43 UTCEPSS rescore
  13. 2026-10-04 23:22 UTCEPSS rescore
  14. 2026-10-03 16:16 UTCEG score recompute
  15. 2026-10-03 16:16 UTCGHSA enrichment
  16. 2026-10-03 14:26 UTCEPSS rescore
  17. 2026-10-02 17:57 UTCEPSS rescore
  18. 2026-10-01 19:50 UTCEPSS rescore
  19. 2026-09-30 15:04 UTCEPSS rescore
  20. 2026-09-30 06:19 UTCEG score recompute
  21. 2026-09-30 06:19 UTCGHSA enrichment
  22. 2026-09-28 13:52 UTCEPSS rescore
  23. 2026-09-27 13:48 UTCEPSS rescore
  24. 2026-09-26 21:29 UTCEG score recompute
  25. 2026-09-26 21:29 UTCGHSA enrichment
Show 48 more
  1. 2026-09-26 15:59 UTCEPSS rescore
  2. 2026-09-26 00:28 UTCEPSS rescore
  3. 2026-09-24 14:04 UTCEPSS rescore
  4. 2026-09-23 17:54 UTCEPSS rescore
  5. 2026-09-22 23:40 UTCEG score recompute
  6. 2026-09-22 23:40 UTCGHSA enrichment
  7. 2026-09-22 16:01 UTCEPSS rescore
  8. 2026-09-21 21:09 UTCEPSS rescore
  9. 2026-09-20 20:16 UTCEPSS rescore
  10. 2026-09-19 19:49 UTCEG score recompute
  11. 2026-09-19 19:49 UTCGHSA enrichment
  12. 2026-09-18 19:28 UTCEPSS rescore
  13. 2026-09-16 16:01 UTCEG score recompute
  14. 2026-09-16 16:00 UTCGHSA enrichment
  15. 2026-09-16 14:08 UTCEPSS rescore
  16. 2026-09-16 05:15 UTCEPSS rescore
  17. 2026-09-15 03:12 UTCEPSS rescore
  18. 2026-09-15 03:12 UTCEPSS rescore
  19. 2026-09-13 12:12 UTCEG score recompute
  20. 2026-09-13 12:12 UTCGHSA enrichment
  21. 2026-09-11 14:53 UTCEPSS rescore
  22. 2026-09-11 14:53 UTCEPSS rescore
  23. 2026-09-10 08:24 UTCEG score recompute
  24. 2026-09-10 08:24 UTCGHSA enrichment
  25. 2026-09-08 22:01 UTCEPSS rescore
  26. 2026-09-07 04:32 UTCEG score recompute
  27. 2026-09-07 04:32 UTCGHSA enrichment
  28. 2026-09-06 13:48 UTCEPSS rescore
  29. 2026-09-05 15:31 UTCEPSS rescore
  30. 2026-09-04 05:07 UTCEPSS rescore
  31. 2026-09-04 00:45 UTCEG score recompute
  32. 2026-09-04 00:44 UTCGHSA enrichment
  33. 2026-09-02 14:12 UTCEPSS rescore
  34. 2026-09-01 13:54 UTCEPSS rescore
  35. 2026-09-01 04:40 UTCEPSS rescore
  36. 2026-09-01 04:40 UTCEPSS rescore
  37. 2026-08-31 20:54 UTCEG score recompute
  38. 2026-08-30 19:18 UTCEPSS rescore
  39. 2026-08-30 19:17 UTCEPSS rescore
  40. 2026-08-30 01:22 UTCEPSS rescore
  41. 2026-08-29 19:44 UTCEG score recompute
  42. 2026-08-28 21:42 UTCEPSS rescore
  43. 2026-08-27 14:25 UTCEPSS rescore
  44. 2026-08-26 15:56 UTCEG score recompute
  45. 2026-08-26 14:47 UTCEPSS rescore
  46. 2026-08-26 12:19 UTCEG score recompute
  47. 2026-08-25 23:25 UTCEG score recompute
  48. 2026-08-25 23:24 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-80199?
CVE-2026-80199 is a low vulnerability published on August 25, 2026. Kimai before 2.54.0 contains a timing oracle vulnerability in TokenAuthenticator that allows unauthenticated attackers to enumerate valid usernames via X-AUTH-USER header. Attackers can measure response time differences when the password hasher runs only for existing users, enabling username…
When was CVE-2026-80199 disclosed?
CVE-2026-80199 was first published on August 25, 2026, with the most recent update on October 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80199 actively exploited?
CVE-2026-80199 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-80199?
CVE-2026-80199 has a CVSS base score of 3.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-80199?
A fix for CVE-2026-80199 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-80199 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-80199

Explore →

Is Your Infrastructure Affected by CVE-2026-80199?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs