# CVE-2026-76647: Leantime JSON-RPC API contains a missing authorization vulnerability

> An authenticated user can bypass authorization in the JSON-RPC dispatcher to modify other users' accounts and take over their sessions.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-62fx-wqcf-qg97

## What is CVE-2026-76647?

CVE-2026-76647 is a high-severity missing authorization vulnerability in Leantime JSON-RPC API, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Leantime JSON-RPC API through version 3.9.0 contains a missing authorization vulnerability in the JSON-RPC dispatcher in app/Domain/Api/Controllers/Jsonrpc.php. The dispatcher does not enforce authorization before invoking service-layer methods, allowing an authenticated user to call methods or act on resources outside their intended permissions. For example, the editOwn method accepts a user-supplied user ID without verifying that it belongs to the caller, allowing an attacker to modify another user's account and set a new password, resulting in account takeover. This vulnerability is distinct from CVE-2026-59712 and CVE-2026-15509 because the root cause is the lack of centralized authorization enforcement in the JSON-RPC dispatcher rather than the behavior of an individual exposed method.

Weakness: CWE-862 (Missing Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-76647?


## How do I fix CVE-2026-76647?

No fix has been published for CVE-2026-76647 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-76647 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-76647 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-76647 and fix it if it is affected.

What it is: CVE-2026-76647 is a high-severity missing authorization vulnerability in Leantime JSON-RPC API, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-76647 exists.

Affected product: Leantime JSON-RPC API. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-76647/ (Markdown: https://insights.sbomify.com/CVE-2026-76647/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-76647
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-76647
- OSV: https://osv.dev/vulnerability/CVE-2026-76647

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-76647/
Summaries are generated and may contain mistakes; the official description above is the record.