# CVE-2026-59713: Leantime - OIDC Login CSRF via Unconditional State Verification Stub

> Attackers can force victims into attacker-controlled sessions via OIDC login CSRF due to missing state validation in Leantime.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Jul 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-vwm8-rprj-29f7

## What is CVE-2026-59713?

CVE-2026-59713 is a high-severity vulnerability in Leantime, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Leantime contains an OIDC login CSRF vulnerability in the verifyState() method that unconditionally returns true without validating state parameters. Attackers can craft malicious callback URLs with attacker-controlled authorization codes to perform session fixation, logging victims in as the attacker.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-59713 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59713 is a high-severity vulnerability in Leantime, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-59713 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-59713/ (Markdown: https://insights.sbomify.com/CVE-2026-59713/index.md)
```

## Sources

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

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