CVE-2026-66412: Leantime broken access control in tickets.getMilestone endpoint

CVE-2026-66412 · Severity: medium · CVSS 6.5 · Published 2026-07-27

Leantime, a project management system, contains a security flaw that allows any logged-in user to view project milestones they are not authorized to see. By guessing milestone identification numbers, an attacker can access sensitive project planning information, including titles, descriptions, and timelines across the entire organization. This could lead to the exposure of strategic roadmaps and internal project details to unauthorized employees or compromised accounts.

Technologies: Leantime. Vendors: Leantime.

Quick answers

Is CVE-2026-66412 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-66412 being exploited in the wild.
How severe is CVE-2026-66412?
Medium severity, with a CVSS score of 6.5, published 27 July 2026.
Which products and versions are affected?
Leantime <= 3.6.2.
Is there a fix for CVE-2026-66412?
A patch was published on 2026-07-19: Fix merged into master branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-66412 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-66412?
Check whether you run Leantime at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A broken access control vulnerability (Insecure Direct Object Reference) exists in the `tickets.getMilestone` JSON-RPC endpoint of Leantime. The `getMilestone()` method in `app/Domain/Tickets/Services/Tickets.php` lacked a project ownership check, only verifying general ticket-read permissions. An authenticated attacker can supply arbitrary integer milestone IDs to the API to retrieve sensitive data, including milestone titles, descriptions, and timelines, regardless of their project membership. The issue is resolved by adding a project assignment verification check using `isUserAssignedToProject()` before returning data.

Affected products

  • Leantime Leantime <= 3.6.2

Timeline

  • 2026-07-17: disclosed: Initial pull request and fix submitted by researcher
  • 2026-07-19: patched: Fix merged into master branch
  • 2026-07-27: advisory: NVD and VulnCheck advisories published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.