CVE-2026-76647: Leantime JSON-RPC API · Missing Authorization
Affects Leantime JSON-RPC APISource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LeantimeJSON-RPC API | Affected
| Fixed in– |
AI-suggested
Until a fix is available, restrict access to the JSON-RPC API to trusted users only and monitor for suspicious activity related to account modifications. Implement additional access controls or compensating controls if possible.
Description
Leantime JSON-RPC API versions up to 3.8.0 have a missing authorization vulnerability in the JSON-RPC dispatcher. This flaw allows authenticated users to invoke service-layer methods without proper permission checks, enabling actions such as modifying other users' accounts and resetting passwords. The vulnerability arises from the dispatcher not enforcing centralized authorization, distinct from other known CVEs affecting Leantime. This can lead to account takeover and full compromise of affected user accounts.