CVE-2026-66412

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH 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 — 4 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(high)
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
15%
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 12× in last 7d / 12× 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-07-28 16:31 UTCEG score recompute
  2. 2026-07-28 16:31 UTCGHSA enrichment
  3. 2026-07-28 15:37 UTCEPSS rescore
  4. 2026-07-28 01:30 UTCEG score recompute
  5. 2026-07-28 01:30 UTCGHSA enrichment
  6. 2026-07-27 18:21 UTCEG score recompute
  7. 2026-07-27 18:21 UTCGHSA enrichment
  8. 2026-07-27 18:11 UTCEG score recompute
  9. 2026-07-27 18:11 UTCGHSA enrichment
  10. 2026-07-27 07:22 UTCEG score recompute
  11. 2026-07-27 06:23 UTCEG score recompute
  12. 2026-07-27 06:22 UTCMITRE cvelistV5first tracked

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 84.9% 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.

Start Free Scan →Browse All CVEs