CVE-2026-66412

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

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

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

Leantime 3.6.2 and prior contains a broken access control vulnerability that allows authenticated users to read milestone data from projects they are not assigned to by supplying arbitrary integer milestone IDs to the tickets.getMilestone JSON-RPC endpoint. Attackers can enumerate integer milestone IDs through the JSON-RPC API to access project planning information, milestone titles, descriptions, and timelines across all projects on the instance regardless of project membership.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
45(Track)
EG Risk 45/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
Severity65% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
24%
KEV
Not listed

Published

July 27, 2026

Last Modified

July 28, 2026

Advisory Details (3)

Auto-updated Jul 27, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr, github_commit.
generic

Leantime all versions prior to and 3.6.2 Broken Access Control via tickets.getMilestone JSON-RPC | Advisories | VulnCheck

https://www.vulncheck.com/advisories/leantime-all-versions-prior-to-and-broken-access-control-via-tickets-getmilestone-json-rpc
github_commit

commit 68898eeb9148 (Leantime/leantime)

Fix landed in Leantime/leantime commit 68898eeb9148 — awaiting tagged release

https://github.com/Leantime/leantime/commit/68898eeb914882a21797523f2782914795bc67ae
github_pr

fix: add project ownership check to getMilestone() to prevent IDOR (CWE-639)

Fix merged in Leantime/leantime PR #3657 on 2026-07-19 — awaiting tagged release

https://github.com/Leantime/leantime/pull/3657

Vendor Advisories for CVE-2026-66412(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 14× in last 7d / 67× 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.

Showing the most recent 100 of 147 total refreshes for this CVE.

  1. 2026-09-20 20:16 UTCEPSS rescore
  2. 2026-09-19 08:27 UTCEG score recompute
  3. 2026-09-19 08:27 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 07:24 UTCEG score recompute
  6. 2026-09-18 07:24 UTCGHSA enrichment
  7. 2026-09-17 09:11 UTCEG score recompute
  8. 2026-09-17 09:11 UTCGHSA enrichment
  9. 2026-09-16 14:08 UTCEPSS rescore
  10. 2026-09-16 07:30 UTCEG score recompute
  11. 2026-09-16 07:30 UTCGHSA enrichment
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-15 09:16 UTCEG score recompute
  14. 2026-09-15 09:16 UTCGHSA enrichment
  15. 2026-09-14 03:19 UTCEG score recompute
  16. 2026-09-14 03:19 UTCGHSA enrichment
  17. 2026-09-13 05:06 UTCEG score recompute
  18. 2026-09-13 05:06 UTCGHSA enrichment
  19. 2026-09-12 06:52 UTCEG score recompute
  20. 2026-09-12 06:52 UTCGHSA enrichment
  21. 2026-09-11 14:53 UTCEPSS rescore
  22. 2026-09-11 09:37 UTCEPSS rescore
  23. 2026-09-11 08:35 UTCGHSA enrichment
  24. 2026-09-10 10:21 UTCEG score recompute
  25. 2026-09-10 10:21 UTCGHSA enrichment
Show 75 more
  1. 2026-09-09 08:27 UTCEG score recompute
  2. 2026-09-09 08:27 UTCGHSA enrichment
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 21:06 UTCEG score recompute
  5. 2026-09-07 21:06 UTCGHSA enrichment
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-06 17:30 UTCEG score recompute
  8. 2026-09-06 17:30 UTCGHSA enrichment
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-05 19:17 UTCEG score recompute
  11. 2026-09-05 19:17 UTCGHSA enrichment
  12. 2026-09-05 15:31 UTCEPSS rescore
  13. 2026-09-04 12:37 UTCEG score recompute
  14. 2026-09-04 12:37 UTCGHSA enrichment
  15. 2026-09-04 05:07 UTCEPSS rescore
  16. 2026-09-02 14:12 UTCEPSS rescore
  17. 2026-09-01 23:05 UTCEG score recompute
  18. 2026-09-01 23:05 UTCGHSA enrichment
  19. 2026-09-01 13:54 UTCEPSS rescore
  20. 2026-09-01 04:40 UTCEPSS rescore
  21. 2026-08-30 22:12 UTCEG score recompute
  22. 2026-08-30 22:12 UTCGHSA enrichment
  23. 2026-08-30 19:17 UTCEPSS rescore
  24. 2026-08-30 01:22 UTCEPSS rescore
  25. 2026-08-29 23:58 UTCEG score recompute
  26. 2026-08-29 23:58 UTCGHSA enrichment
  27. 2026-08-28 21:42 UTCEPSS rescore
  28. 2026-08-27 09:48 UTCEG score recompute
  29. 2026-08-27 09:47 UTCGHSA enrichment
  30. 2026-08-26 14:47 UTCEPSS rescore
  31. 2026-08-26 10:38 UTCEG score recompute
  32. 2026-08-26 10:38 UTCGHSA enrichment
  33. 2026-08-25 13:49 UTCEPSS rescore
  34. 2026-08-25 11:34 UTCEG score recompute
  35. 2026-08-25 11:34 UTCGHSA enrichment
  36. 2026-08-24 13:21 UTCEG score recompute
  37. 2026-08-24 13:21 UTCGHSA enrichment
  38. 2026-08-23 15:07 UTCEG score recompute
  39. 2026-08-23 15:07 UTCGHSA enrichment
  40. 2026-08-23 00:19 UTCEPSS rescore
  41. 2026-08-22 16:54 UTCEG score recompute
  42. 2026-08-22 16:54 UTCGHSA enrichment
  43. 2026-08-21 23:49 UTCEPSS rescore
  44. 2026-08-21 18:40 UTCEG score recompute
  45. 2026-08-21 18:40 UTCGHSA enrichment
  46. 2026-08-20 22:56 UTCEPSS rescore
  47. 2026-08-20 20:26 UTCGHSA enrichment
  48. 2026-08-19 22:13 UTCEG score recompute
  49. 2026-08-19 22:13 UTCGHSA enrichment
  50. 2026-08-19 17:04 UTCEPSS rescore
  51. 2026-08-18 23:58 UTCEG score recompute
  52. 2026-08-18 23:58 UTCGHSA enrichment
  53. 2026-08-18 13:48 UTCEPSS rescore
  54. 2026-08-18 01:44 UTCEG score recompute
  55. 2026-08-18 01:44 UTCGHSA enrichment
  56. 2026-08-17 13:47 UTCEPSS rescore
  57. 2026-08-17 03:31 UTCEG score recompute
  58. 2026-08-17 03:31 UTCGHSA enrichment
  59. 2026-08-16 14:56 UTCEPSS rescore
  60. 2026-08-16 05:18 UTCEG score recompute
  61. 2026-08-16 05:18 UTCGHSA enrichment
  62. 2026-08-15 07:05 UTCEG score recompute
  63. 2026-08-15 07:05 UTCGHSA enrichment
  64. 2026-08-15 01:30 UTCEPSS rescore
  65. 2026-08-14 08:51 UTCEG score recompute
  66. 2026-08-14 08:51 UTCGHSA enrichment
  67. 2026-08-13 22:00 UTCEPSS rescore
  68. 2026-08-13 10:38 UTCEG score recompute
  69. 2026-08-13 10:38 UTCGHSA enrichment
  70. 2026-08-12 13:51 UTCEPSS rescore
  71. 2026-08-12 12:25 UTCGHSA enrichment
  72. 2026-08-11 14:11 UTCEG score recompute
  73. 2026-08-11 14:11 UTCGHSA enrichment
  74. 2026-08-11 00:00 UTCEPSS rescore
  75. 2026-08-10 15:58 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-66412?
CVE-2026-66412 is a medium vulnerability published on July 27, 2026. Leantime 3.6.2 and prior contains a broken access control vulnerability that allows authenticated users to read milestone data from projects they are not assigned to by supplying arbitrary integer milestone IDs to the tickets.getMilestone JSON-RPC endpoint. Attackers can enumerate integer milestone…
When was CVE-2026-66412 disclosed?
CVE-2026-66412 was first published in the National Vulnerability Database on July 27, 2026, with the most recent update on July 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-66412 actively exploited?
CVE-2026-66412 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 75.5% of all scored CVEs.
What is the CVSS score of CVE-2026-66412?
CVE-2026-66412 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-66412?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-66412, 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-66412

Explore →

Is Your Infrastructure Affected by CVE-2026-66412?

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