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.
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Sun, 08 Nov 2026 01:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Vikunja veans before 2.7.1 Credential Leak via Repo-Controlled .veans.yml Server | |
| First Time appeared |
Vikunja
Vikunja vikunja |
|
| Weaknesses | CWE-346 | |
| CPEs | cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Vikunja
Vikunja vikunja |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-11-08T01:37:16.315Z
Reserved: 2026-11-06T00:45:39.026Z
Link: CVE-2026-123499
No data.
Status : Deferred
Published: 2026-11-08T02:16:37.510
Modified: 2026-11-08T02:16:37.633
Link: CVE-2026-123499
No data.
OpenCVE Enrichment
Updated: 2026-11-08T05:00:17Z
Weaknesses