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


- **Severity:** Medium 4.8 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 8 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-5mwr-g4r9-hv44, GHSA-rxwp-q2qg-98vw

## What is CVE-2026-123496?

CVE-2026-123496 is a medium-severity vulnerability in go-vikunja vikunja, published on 8 Nov 2026. 

### Official 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.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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


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

No fix has been published for CVE-2026-123496 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-123496 being exploited?

There is no known exploitation of CVE-2026-123496 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-123496 and fix it if it is affected.

What it is: CVE-2026-123496 is a medium-severity vulnerability in go-vikunja vikunja, published on 8 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123496 in the wild and no public exploit code.

Affected product: go-vikunja vikunja. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-123496/ (Markdown: https://insights.sbomify.com/CVE-2026-123496/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-123496
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-123496
- OSV: https://osv.dev/vulnerability/CVE-2026-123496

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-123496/
Summaries are generated and may contain mistakes; the official description above is the record.