CVE-2026-123499go-vikunja vikunja
NVD
Vulnerability Summary
Vikunja veans before 2.7.1 contains a credential exposure vulnerability that allows malicious repository authors to capture API tokens by specifying an attacker-controlled server in .veans.yml. When veans runs in an untrusted checkout, it sends VEANS_TOKEN as a Bearer token, or login passwords, TOTP codes and tokens, to that server, granting attackers the victim's Vikunja access.
CVSS v4.0 Base Metrics — Score 6.0 (MEDIUM)
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:NAttack VectorNetwork
Attack ComplexityHigh
Attack RequirementsPresent
Privileges RequiredNone
User InteractionPassive
Confidentiality (Vulnerable System)High
Integrity (Vulnerable System)Low
Availability (Vulnerable System)None
Confidentiality (Subsequent System)None
Integrity (Subsequent System)None
Availability (Subsequent System)None
Show CVSS v3.x metrics (score 5.9)
CVSS v3.1 Base Metrics — Score 5.9 (MEDIUM)
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:NAttack VectorNetwork
Attack ComplexityHigh
Privileges RequiredNone
User InteractionRequired
ScopeUnchanged
ConfidentialityHigh
IntegrityLow
AvailabilityNone
Affected & Patched Versions
- go-vikunja vikunja < 2.7.1
- go-vikunja vikunja 2.7.1
What to do
Fix it during your normal patch cycle. No exploitation is confirmed yet.
- 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 11, 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-123499. 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:22 UTC