CVE-2026-123496 · AI agents & MCP
NO FIX YET · SEE WHAT TO DO
Before version 2.7.1, the veans CLI's init command follows symlinks in a crafted repository, so it writes files outside the project. An attacker can use this to overwrite user files such as ~/.bashrc or install veans hooks and plugins globally.
first public Oct 22, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams that run veans init on repositories they did not write, such as cloned or third-party code, are exposed. Reading the sources, a repository is the attack vector, so teams that only use veans on their own trusted repositories have lower exposure. unknown for any other deployment detail.
Not affected if trusted-repos-only, veans-2.7.1-or-later
Who cares claude-code, opencode, veans, vikunja
veans --version (exact flag unknown from sources)..veans.yml, .claude or .opencode entries in repositories you cloned and ran veans init in.2.7.1 or laterVikunja veans before 2.7.1 contains a symlink following vulnerability that allows attackers to make veans init write files outside the repository via crafted repo symlinks. Attackers can ship symlinked .veans.yml, .claude, or .opencode entries to overwrite user files like ~/.bashrc or install veans hooks and plugins globally.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.