# CVE-2026-27819: Vikunja has Path Traversal in CLI Restore > Attackers can overwrite arbitrary files and crash the application via a malicious ZIP archive during CLI restore operations in Vikunja. - **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 25 Feb 2026 - **Updated:** 26 Feb 2026 - **Also known as:** GHSA-42wg-38gx-85rh, GO-2026-4556 ## What is CVE-2026-27819? CVE-2026-27819 is a high-severity path traversal vulnerability in go-vikunja vikunja, published on 25 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim. ### Official description Vikunja is an open-source self-hosted task management platform. Prior to version 2.0.0, the restoreConfig function in vikunja/pkg/modules/dump/restore.go of the go-vikunja/vikunja repository fails to sanitize file paths within the provided ZIP archive. A maliciously crafted ZIP can bypass the intended extraction directory to overwrite arbitrary files on the host system. Additionally, we’ve discovered that a malformed archive triggers a runtime panic, crashing the process immediately after the database has been wiped permanently. The application trusts the metadata in the ZIP archive. It uses the Name attribute of the zip.File struct directly in os.OpenFile calls without validation, allowing files to be written outside the intended directory. The restoration logic assumes a specific directory structure within the ZIP. When provided with a "minimalist" malicious ZIP, the application fails to validate the length of slices derived from the archive contents. Specifically, at line 154, the code attempts to access an index of len(ms)-2 on an insufficiently populated slice, triggering a panic. Version 2.0.0 fixes the issue. Weakness: CWE-248 (Uncaught Exception), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2026-27819? 3 open source packages ship an affected version, including code.vikunja.io/api. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `code.vikunja.io/api` | Go | All versions | None | | `code.vikunja.io/api` | Go | All versions to 0.24.6 | None | | `code.vikunja.io/api` | Go | All versions to 0.24.6 | None | Products: Vikunja Vikunja. ## How do I fix CVE-2026-27819? Upgrade to a fixed version. ## Is CVE-2026-27819 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27819 exists. ## Other vulnerabilities in go-vikunja vikunja - [CVE-2026-28268](https://insights.sbomify.com/CVE-2026-28268/): Vikunja Vulnerable to Account Takeover via Password Reset Token Reuse (critical 9.8) - [CVE-2026-27575](https://insights.sbomify.com/CVE-2026-27575/): Vijkunja has Weak Password Policy Combined with Persistent Sessions After Password Change (critical 9.1) - [CVE-2026-25935](https://insights.sbomify.com/CVE-2026-25935/): Vikunja Affected by XSS Via Task Preview (high 8.6) - [CVE-2026-35595](https://insights.sbomify.com/CVE-2026-35595/): Vikunja Affected by Privilege Escalation via Project Reparenting (high 8.3) - [CVE-2026-33316](https://insights.sbomify.com/CVE-2026-33316/): Vikunja’s Improper Access Control Enables Bypass of Administrator-Imposed Account Disablement (high 8.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-27819 and fix it if it is affected. What it is: CVE-2026-27819 is a high-severity path traversal vulnerability in go-vikunja vikunja, published on 25 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27819 exists. Affected packages and fixed versions: - code.vikunja.io/api (Go): affected all versions; no fix listed - code.vikunja.io/api (Go): affected all versions up to 0.24.6; no fix listed - code.vikunja.io/api (Go): affected all versions up to 0.24.6; no fix listed 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-27819/ (Markdown: https://insights.sbomify.com/CVE-2026-27819/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-27819 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27819 - OSV: https://osv.dev/vulnerability/CVE-2026-27819 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-27819/ Summaries are generated and may contain mistakes; the official description above is the record.