# CVE-2026-28518: OpenViking .ovpack Import ZIP Slip Path Traversal

> Attackers can exploit path traversal in OpenViking's .ovpack import to write arbitrary files, potentially leading to code execution.

- **Severity:** High 8.4 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Mar 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-rpqr-j937-6qr9, PYSEC-2026-2856

## What is CVE-2026-28518?

CVE-2026-28518 is a high-severity path traversal vulnerability in Volcengine OpenViking, published on 3 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

3 open source packages ship an affected version, including openviking. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openviking` | PyPI | All versions to 0.2.1 | None |
| `openviking` | PyPI | All versions to 0.2.1 | None |
| `openviking` | PyPI | All versions to 0.2.1 | None |

Products: Volcengine Openviking.

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

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

## Is CVE-2026-28518 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28518 exists.

## Other vulnerabilities in Volcengine OpenViking

- [CVE-2026-40525](https://insights.sbomify.com/CVE-2026-40525/): OpenViking < 0.3.9 Authentication Bypass via VikingBot OpenAPI (critical 9.1)
- [CVE-2026-22680](https://insights.sbomify.com/CVE-2026-22680/): OpenViking < 0.3.3 Missing Authorization via Task Polling (medium 6.9)
- [CVE-2026-34999](https://insights.sbomify.com/CVE-2026-34999/): OpenViking 0.2.5 < 0.2.14 Bot Proxy Endpoints Allow Unauthenticated Access (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-28518 is a high-severity path traversal vulnerability in Volcengine OpenViking, published on 3 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28518 exists.

Affected packages and fixed versions:
- openviking (PyPI): affected all versions up to 0.2.1; no fix listed
- openviking (PyPI): affected all versions up to 0.2.1; no fix listed
- openviking (PyPI): affected all versions up to 0.2.1; 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-28518/ (Markdown: https://insights.sbomify.com/CVE-2026-28518/index.md)
```

## Sources

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

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