---
id: "CVE-2026-123499"
page: "https://infrastack.ai/live/CVE-2026-123499"
kind: "vulnerability"
aliases: ["CVE-2026-123499"]
title: "Vikunja veans: malicious repo config leaks API tokens to attacker server"
severity: "medium"
cvss: 6.0
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["ci", "developers", "package", "veans", "vikunja"]
not_affected_if: ["trusted-repos-only"]
published_at: "2026-11-08T02:16:37+00:00"
first_seen_at: "2026-11-08T02:21:08+00:00"
updated_at: "2026-11-08T02:25:12+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-123499", "first_seen_at": "2026-11-08T02:21:08+00:00"}]
exploit_sources: []
---

# Vikunja veans: malicious repo config leaks API tokens to attacker server

Link for people: https://infrastack.ai/live/CVE-2026-123499 (this .md is for agents)

The veans tool, before version 2.7.1, reads a server address from a .veans.yml file in the repository it runs in. A malicious repository can point that address at an attacker-controlled server, so veans sends the user's Vikunja API token, login password or TOTP code there.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed veans version with `veans --version` and compare it against `2.7.1`.
- Look for a `.veans.yml` file in any checkout you run veans in, and check whether its server address points somewhere unexpected.

## Fix

- veans: move to `2.7.1` or later, per the sources.

## Timeline

- 2026-11-08T02:21:08+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-123499

## Documents

- [advisory] Vendor advisory: github.com https://github.com/go-vikunja/vikunja/security/advisories/GHSA-3rrq-h284-5vpx
- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/vikunja-veans-before-2.7.1-credential-leak-via-repo-controlled-veans-yml-server

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_