Symlink following in Vikunja veans init lets attackers write files
Key facts
- Attack vector
- Local
- Privileges required
- None
- User interaction
- Passive
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- —
- Confidentiality · integrity · availability
- None · Low · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA.
Summary
Vikunja veans before 2.7.1 contains a symlink following flaw that lets attackers make veans init write files outside the repository. Attackers can ship crafted repository symlinks in .veans.yml, .claude, or .opencode entries to overwrite user files such as ~/.bashrc or install veans hooks and plugins globally. A local user with low privileges can exploit it if a user runs veans init in a crafted repository, as shown by CVSS 4.0 user interaction being required.
Written with Claude Haiku 5.5 from the sources below · 2026-11-08
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| go-vikunja | vikunja | before 2.7.1 | 2.7.1 | Patch available | CNA |
- vikunja Vendorgo-vikunja Affected before 2.7.1 Fixed in 2.7.1 Patch available CNA
CPE names Threatist (inferred) · 1
Inferred from how NVD named this product before; not given by a source.
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:* | — | — | go-vikunja |
- cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:* Versions — — ·go-vikunja
Remediation
Upgrade go-vikunja vikunja to version 2.7.1 or later, which fixes the flaw.
Written with Claude Haiku 5.5 from the sources below · 2026-11-08
- Fix · CNA vikunja (go-vikunja) Fixed in 2.7.1
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
go-vikunja vikunja 2.7.1
39 records Highest priority Priority HIGH 2 HIGH, 7 MEDIUM, 30 LOW
Other records, highest priority first
- TI-2026-86673 Uncontrolled resource consumption in Vikunja lets users bypass pagination limitsPriority HIGH 73
- TI-2026-86670 Insufficient session expiration in Vikunja lets revoked tokens authenticatePriority HIGH 68
- TI-2026-86666 Information disclosure in Vikunja webhook related_tasks payloadPriority MEDIUM 64
Timeline
- 2026-11-08 Threatist record created from CVE-2026-123496
- 2026-11-08 Alias added: GHSA-5mwr-g4r9-hv44
- 2026-11-12 CISA SSVC decision points changed
References
More go-vikunja vulnerabilities
- TI-2026-40929 Authorization bypass in go-vikunja Vikunja CVSS 4.0CRITICAL 9.3
- TI-2026-21967 Vijkunja has Weak Password Policy Combined with Persistent Sessions After Password Change CVSS 3.1CRITICAL 9.1
- TI-2026-62115 Vikunja before 2.6.0 Privilege Escalation via Link Share Hash CVSS 4.0HIGH 8.7
- TI-2026-62108 Vikunja before 2.6.0 Authentication Bypass via CalDAV BasicAuth CVSS 4.0HIGH 8.7
- TI-2026-62107 Vikunja before 2.6.0 Authentication Bypass via Unthrottled API CVSS 4.0HIGH 8.7
- TI-2026-26971 Vikunja ahs a TOTP Two-Factor Authentication Bypass via OIDC Login Path CVSS 3.1CRITICAL 9.1
Sources
- CVE-2026-123496 · CVE Program
- CVE-2026-123496 · NVD
- FIRST EPSS
- GHSA-5mwr-g4r9-hv44 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences