● High · CVSS 8.4

How to Fix CVE-2026-28518: Path traversal in OpenViking

Q: Is CVE-2026-28518 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.

Q: Do I need to reboot after patching CVE-2026-28518?

For kernel and OS-level updates, yes. For most userland packages a `systemctl restart ` 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.

Q: What is the CVSS score for CVE-2026-28518?

8.4 (High). Vector: `CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`.

Q: Where is the official advisory for CVE-2026-28518?

The vendor advisory is at [https://github.com/volcengine/OpenViking/issues/342](https://github.com/volcengine/OpenViking/issues/342). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-28518.

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

CVE-2026-28518 is a path traversal in Volcengine OpenViking. The fix is to upgrade to OpenViking 46b3e76e28b9b3eee73693720c9ec48820228b72.

⚡ At a glance


Severity	8.4 (High)
Actively exploited?	No public listing in CISA KEV
Affected	OpenViking 0 to <=0.2.1
Fixed in	OpenViking 46b3e76e28b9b3eee73693720c9ec48820228b72
Type (CWE)	CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

What is CVE-2026-28518?

OpenViking versions 0.2.1 and prior, fixed in commit 46b3e76, contain a path traversal vulnerability in the .ovpack import handling that allows attackers to write files outside the intended import directory. Attackers can craft malicious ZIP archives with traversal sequences, absolute paths, or drive prefixes in member names to overwrite or create arbitrary files with the importing process privileges. The CVSS base score is 8.4 (High), which puts this in the upper risk band and warrants a fast patch cycle. The official advisory is at https://github.com/volcengine/OpenViking/issues/342.

Am I affected?

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

Run the version check that fits your platform:


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


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

How to fix CVE-2026-28518

Upgrade OpenViking to a patched build: OpenViking 46b3e76e28b9b3eee73693720c9ec48820228b72. 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 openviking
dpkg -s openviking | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


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

SUSE / openSUSE


sudo zypper refresh
sudo zypper update openviking
rpm -q openviking

Complete PowerShell remediation script (Windows)


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

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-28518-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 "*OpenViking*" -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\openviking-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\OpenViking" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to OpenViking 46b3e76e28b9b3eee73693720c9ec48820228b72"
    winget upgrade --name "OpenViking" --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 "OpenViking"
    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-28518 affecting OpenViking
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-28518-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 openviking 2>/dev/null | grep -i ^Version || echo "openviking not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q openviking || echo "openviking not installed via rpm"
fi

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

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

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s openviking 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q openviking
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-28518" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-28518"

Disable the affected service (Linux)


sudo systemctl stop openviking 2>/dev/null || true
sudo systemctl disable openviking 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 openviking 2>/dev/null | grep -i ^Version
rpm -q openviking 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 "*OpenViking*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above OpenViking 46b3e76e28b9b3eee73693720c9ec48820228b72. 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:

How to Fix CVE-2026-44479: Information Disclosure in vercel — Information Disclosure in vercel
How to Fix CVE-2026-0798: Access Control Bypass in Gitea Open Source Git Server — Access Control Bypass in Gitea Open Source Git Server
How to Fix CVE-2026-44309: Authentication Bypass in gitsign , Authentication Bypass in gitsign
How to Fix CVE-2026-32010: OpenClaw < 2026.2.22 - Allowlist Bypass via sort --compress-program Parameter , OpenClaw < 2026.2.22 - Allowlist Bypass via sort --compress-program Parameter
How to Fix CVE-2026-48222: Cross-Site Scripting in Tickets , Cross-Site Scripting in Tickets

Is CVE-2026-28518 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-28518?

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-28518?

8.4 (High). Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N.

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

The vendor advisory is at https://github.com/volcengine/OpenViking/issues/342. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-28518.

References

Official vendor advisory: https://github.com/volcengine/OpenViking/issues/342
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-28518
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
Additional reference: https://github.com/volcengine/OpenViking/commit/46b3e76e28b9b3eee73693720c9ec48820228b72
Additional reference: https://www.vulncheck.com/advisories/openviking-ovpack-import-zip-slip-path-traversal

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