CVE-2026-59713: Leantime contains an OIDC login CSRF vulnerability in the verifyState() method that unconditionally
Source GCVE Database
Not known to be exploited · CVSS 8.1 High.
Data as of 26 Oct 2026, 15:59 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 6 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
AI-suggested
Users should monitor vendor advisories for updates. Until a fix is provided, caution should be exercised when handling OIDC login flows, and additional validation or protective controls should be considered if possible.
Description
Leantime has a security vulnerability in its OIDC login implementation where the verifyState() method does not properly validate state parameters, always returning true. This flaw allows attackers to craft malicious callback URLs with attacker-controlled authorization codes, enabling session fixation attacks that log victims in as the attacker.
References
- nvd.nist.gov/vuln/detail/CVE-2026-59713 (opens in a new tab)
- github.com/Leantime/leantime/issues/3535 (opens in a new tab)
- github.com/Leantime/leantime/commit/9630eb7db682fb1b4e23cdabf3428d03ec6f5094 (opens in a new tab)
- github.com/Leantime/leantime (opens in a new tab)
- vulncheck.com/advisories/leantime-oidc-login-csrf-via-unconditional-state-verification-stub (opens in a new tab)