⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● High · CVSS 7.2

How to Fix CVE-2026-27819: Path traversal in vikunja

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-27819 is a path traversal in go-vikunja vikunja. The fix is to apply the vendor patch noted below.

⚡ At a glance
Severity7.2 (High)
Actively exploited?No public listing in CISA KEV
Affectedvikunja < 2.0.0
Fixed inSee vendor advisory
Type (CWE)CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

What is CVE-2026-27819?

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. The CVSS base score is 7.2 (High), which puts this in the upper risk band and warrants a fast patch cycle. The official advisory is at https://github.com/go-vikunja/vikunja/security/advisories/GHSA-42wg-38gx-85rh.

Am I affected?

Check the version of vikunja you are running and compare it against the Affected row above (vikunja < 2.0.0). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


# Linux package check
dpkg -s vikunja 2>/dev/null | grep -i ^Version
rpm -q vikunja 2>/dev/null
command -v vikunja >/dev/null && vikunja --version 2>/dev/null


# Windows (PowerShell)
Get-Package -Name "*vikunja*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "vikunja" 2>$null

How to fix CVE-2026-27819

Upgrade vikunja to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade vikunja
dpkg -s vikunja | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh vikunja -y
# or for older releases:
sudo yum update vikunja -y
rpm -q vikunja

SUSE / openSUSE


sudo zypper refresh
sudo zypper update vikunja
rpm -q vikunja

Node.js / npm


# Update the affected package in your project
npm install vikunja@latest
npm ls vikunja
npm audit fix

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-27819 affecting vikunja
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-27819-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detect installed version"
    $pkg = Get-Package -Name "*vikunja*" -ErrorAction SilentlyContinue
    if ($pkg) { $pkg | Format-Table Name, Version }
    else { Write-Host "Not detected via Get-Package; try winget list" }

    Write-Host "[2/4] Backup configuration"
    $backup = "C:\Backup\vikunja-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\vikunja" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "vikunja" --silent --accept-source-agreements --accept-package-agreements
    if ($LASTEXITCODE -ne 0) {
        # Fallback: pull latest via OS update channel
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verify the patched build"
    winget list --name "vikunja"
    Write-Host "Patch applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)


#!/usr/bin/env bash
# Fix script for CVE-2026-27819 affecting vikunja
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-27819-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
    dpkg -s vikunja 2>/dev/null | grep -i ^Version || echo "vikunja not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q vikunja || echo "vikunja not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-27819-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/vikunja /etc/vikunja.d /etc/vikunja.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y vikunja
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y vikunja
elif command -v yum >/dev/null; then
    yum update -y vikunja
elif command -v zypper >/dev/null; then
    zypper --non-interactive update vikunja
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s vikunja 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q vikunja
fi
echo "Done. Restart any service that loaded the old library."

If you can't patch immediately

Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.

Restrict exposure with nftables (Linux)


# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Block at the host firewall (Windows)


New-NetFirewallRule -DisplayName "Block-CVE-2026-27819" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-27819"

Disable the affected service (Linux)


sudo systemctl stop vikunja 2>/dev/null || true
sudo systemctl disable vikunja 2>/dev/null || true

If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.

How to verify the fix worked

After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.


# Linux
dpkg -s vikunja 2>/dev/null | grep -i ^Version
rpm -q vikunja 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true


# Windows
Get-Package -Name "*vikunja*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

Is CVE-2026-27819 actively exploited?

There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.

Do I need to reboot after patching CVE-2026-27819?

For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.

What is the CVSS score for CVE-2026-27819?

7.2 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H.

Where is the official advisory for CVE-2026-27819?

The vendor advisory is at https://github.com/go-vikunja/vikunja/security/advisories/GHSA-42wg-38gx-85rh. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-27819.

References

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*