CVE-2026-123513go-vikunja vikunja
NVD
Vulnerability Summary
Vikunja before 2.7.1 contains a credential exposure vulnerability that allows attackers to steal stored auth tokens by inducing users to switch the frontend API URL. Because checkAndSetApiUrl leaves origin-independent localStorage tokens in place, the bearer token and desktop OAuth refresh token are sent to the attacker's server, enabling account takeover.
CVSS v4.0 Base Metrics — Score 7.6 (HIGH)
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NAttack VectorNetwork
Attack ComplexityHigh
Attack RequirementsPresent
Privileges RequiredNone
User InteractionPassive
Confidentiality (Vulnerable System)High
Integrity (Vulnerable System)High
Availability (Vulnerable System)None
Confidentiality (Subsequent System)None
Integrity (Subsequent System)None
Availability (Subsequent System)None
Show CVSS v3.x metrics (score 6.8)
CVSS v3.1 Base Metrics — Score 6.8 (MEDIUM)
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:NAttack VectorNetwork
Attack ComplexityHigh
Privileges RequiredNone
User InteractionRequired
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
Affected & Patched Versions
- go-vikunja vikunja < 2.7.1
- go-vikunja vikunja 2.7.1
What to do
Plan remediation soon. No exploitation is confirmed yet, but the severity is high.
- Check whether you run go-vikunja vikunja and which version.
- Update to a patched version listed above, then confirm the new version.
Timeline
- Nov 8, 2026Published
- Nov 10, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get notified about new go-vikunja vikunja CVEsYou are reading CVE-2026-123513. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsExternal References
Data last checked: Nov 14, 2026 03:11 UTC