CVE-2026-54418

HIGHPre-NVD 8.18.1
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-05. a secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Leantime through 3.6.2 exposes the JSON-RPC methods leantime.rpc.TwoFA.TwoFA.getSetupData, saveSecret, verifyAndEnable, and disable2FA, which act on a caller-supplied userId parameter with no ownership check, session pinning, or permission-attribute gate (unlike other RPC-exposed methods in the same dispatcher).

CVSS v3
8.1
EG Score
8.1(high)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

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
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

August 5, 2026

Last Modified

August 10, 2026

Advisory Details (1)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

GitHub - Leantime/leantime: Leantime is a goals focused project management system for non-project managers. Building with ADHD, Autism, and dyslexia in mind. · GitHub

https://github.com/Leantime/leantime

Vendor Advisories for CVE-2026-54418(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 29× in last 7d / 73× 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-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 21:03 UTCGHSA enrichment
  3. 2026-08-20 09:47 UTCGHSA enrichment
  4. 2026-08-19 22:33 UTCEG score recompute
  5. 2026-08-19 22:33 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 11:19 UTCGHSA enrichment
  8. 2026-08-19 00:05 UTCEG score recompute
  9. 2026-08-19 00:05 UTCGHSA enrichment
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-18 12:49 UTCGHSA enrichment
  12. 2026-08-18 00:58 UTCEG score recompute
  13. 2026-08-18 00:58 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 13:09 UTCGHSA enrichment
  16. 2026-08-17 01:55 UTCEG score recompute
  17. 2026-08-17 01:55 UTCGHSA enrichment
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 14:41 UTCGHSA enrichment
  20. 2026-08-16 03:27 UTCEG score recompute
  21. 2026-08-16 03:27 UTCGHSA enrichment
  22. 2026-08-16 02:14 UTCEPSS rescore
  23. 2026-08-15 16:13 UTCGHSA enrichment
  24. 2026-08-15 04:59 UTCEG score recompute
  25. 2026-08-15 04:59 UTCGHSA enrichment
Show 48 more
  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-14 17:45 UTCGHSA enrichment
  3. 2026-08-14 06:20 UTCEG score recompute
  4. 2026-08-14 06:20 UTCGHSA enrichment
  5. 2026-08-13 22:00 UTCEPSS rescore
  6. 2026-08-13 19:06 UTCGHSA enrichment
  7. 2026-08-13 07:52 UTCGHSA enrichment
  8. 2026-08-12 20:38 UTCEG score recompute
  9. 2026-08-12 20:38 UTCGHSA enrichment
  10. 2026-08-12 13:51 UTCEPSS rescore
  11. 2026-08-12 09:25 UTCGHSA enrichment
  12. 2026-08-11 22:11 UTCEG score recompute
  13. 2026-08-11 22:11 UTCGHSA enrichment
  14. 2026-08-11 10:53 UTCEG score recompute
  15. 2026-08-11 10:53 UTCGHSA enrichment
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-10 23:39 UTCGHSA enrichment
  18. 2026-08-10 12:25 UTCEG score recompute
  19. 2026-08-10 12:25 UTCGHSA enrichment
  20. 2026-08-10 12:04 UTCGHSA enrichment
  21. 2026-08-10 11:23 UTCEG score recompute
  22. 2026-08-10 11:23 UTCGHSA enrichment
  23. 2026-08-10 05:46 UTCGHSA enrichment
  24. 2026-08-09 18:33 UTCEG score recompute
  25. 2026-08-09 18:33 UTCGHSA enrichment
  26. 2026-08-09 13:46 UTCEPSS rescore
  27. 2026-08-09 07:19 UTCGHSA enrichment
  28. 2026-08-08 20:05 UTCEG score recompute
  29. 2026-08-08 20:05 UTCGHSA enrichment
  30. 2026-08-08 16:37 UTCEPSS rescore
  31. 2026-08-08 08:51 UTCGHSA enrichment
  32. 2026-08-07 21:38 UTCEG score recompute
  33. 2026-08-07 21:38 UTCGHSA enrichment
  34. 2026-08-07 10:24 UTCGHSA enrichment
  35. 2026-08-06 23:10 UTCEG score recompute
  36. 2026-08-06 23:10 UTCGHSA enrichment
  37. 2026-08-06 13:47 UTCEPSS rescore
  38. 2026-08-06 11:56 UTCGHSA enrichment
  39. 2026-08-06 00:43 UTCEG score recompute
  40. 2026-08-06 00:43 UTCGHSA enrichment
  41. 2026-08-05 19:17 UTCEPSS rescore
  42. 2026-08-05 13:29 UTCEG score recompute
  43. 2026-08-05 13:29 UTCGHSA enrichment
  44. 2026-08-05 12:31 UTCEG score recompute
  45. 2026-08-05 12:31 UTCGHSA enrichment
  46. 2026-08-05 08:23 UTCEG score recompute
  47. 2026-08-05 07:23 UTCEG score recompute
  48. 2026-08-05 07:20 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-54418?
CVE-2026-54418 is a high vulnerability published on August 5, 2026. Leantime through 3.6.2 exposes the JSON-RPC methods leantime.rpc.TwoFA.TwoFA.getSetupData, saveSecret, verifyAndEnable, and disable2FA, which act on a caller-supplied userId parameter with no ownership check, session pinning, or permission-attribute gate (unlike other RPC-exposed methods in the…
When was CVE-2026-54418 disclosed?
CVE-2026-54418 was first published in the National Vulnerability Database on August 5, 2026, with the most recent update on August 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54418 actively exploited?
CVE-2026-54418 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.6% of all scored CVEs.
What is the CVSS score of CVE-2026-54418?
CVE-2026-54418 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-54418?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54418, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-54418

Explore →

Is Your Infrastructure Affected by CVE-2026-54418?

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