CVE-2026-123512: vikunja · Sensitive Data in Logs
Affects vikunjaSource CVE Database V5
Not known to be exploited · CVSS 8.4 High : upgrade to 2.7.1 soon.
Data as of 8 Nov 2026, 02:19 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 8.4 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 6.1 |
- Patch
- Available – fixed in 2.7.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Nov 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 7 Nov 2026.
What to do
Upgrade vikunja to 2.7.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| go-vikunjavikunja | Affected
| Fixed in
|
Govikunjapkg:golang/vikunjaOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Vikunja to version 2.7.1 or later, where this vulnerability is fixed. The fix removes sensitive tokens from logged URLs, preventing exposure in logs. No other mitigation is required once the upgrade is applied.
Description
Vikunja versions prior to 2.7.1 include sensitive tokens for password reset, email confirmation, and account deletion in URL query strings sent via email. These URLs are logged in HTTP access logs and reverse-proxy logs. An attacker with access to these logs can replay unredeemed tokens to hijack accounts or confirm account deletions. The vulnerability is fixed in version 2.7.1.