# CVE-2026-54418: Leantime - Missing Authorization on TwoFA JSON-RPC Methods Allows Cross-Account 2FA Secret Disclosure and Bypass

> Attackers can access other users' 2FA secrets and disable their 2FA via JSON-RPC methods lacking ownership checks in Leantime.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **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:** 5 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-j9c4-c6g5-c9fv

## What is CVE-2026-54418?

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

### Official description

Leantime through 3.6.2 exposes the JSON-RPC methods leantime.rpc.TwoFA.TwoFA.getSetupData, saveSecret, verifyAndEnable, and disable2FA, which act on a caller-supplied userId parameter with no ownership check, session pinning, or permission-attribute gate (unlike other RPC-exposed methods in the same dispatcher).

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-54418 being exploited?

There is no known exploitation of CVE-2026-54418 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54418 is a high-severity missing authorization vulnerability in Leantime, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54418 in the wild and no public exploit code.

Affected product: Leantime. 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-54418/ (Markdown: https://insights.sbomify.com/CVE-2026-54418/index.md)
```

## Sources

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

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