Is CVE-2026-28518 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-28518 being exploited in the wild.

How severe is CVE-2026-28518?

High severity, with a CVSS score of 7.8, published 3 March 2026.

Which products and versions are affected?

openviking (PyPI) ECOSYSTEM:introduced=0,last_affected=0.2.1.

Is there a fix for CVE-2026-28518?

A patch was published on 2026-03-03: Fix commit 46b3e76 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-28518 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-28518?

Check whether you run openviking (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-28518: Volcengine OpenViking path traversal in .ovpack import

CVE-2026-28518 · Severity: high · CVSS 7.8 · Published 2026-03-03

OpenViking, an open-source tool for managing AI resources, is vulnerable to a security flaw when importing package files (.ovpack). An attacker can create a specially crafted package that, when imported by a user, writes malicious files to sensitive locations on the user's computer. This could allow an attacker to overwrite system files or execute unauthorized code, potentially leading to a full system compromise.

Technologies: openviking (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-28518 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-28518 being exploited in the wild.
How severe is CVE-2026-28518?: High severity, with a CVSS score of 7.8, published 3 March 2026.
Which products and versions are affected?: openviking (PyPI) ECOSYSTEM:introduced=0,last_affected=0.2.1.
Is there a fix for CVE-2026-28518?: A patch was published on 2026-03-03: Fix commit 46b3e76 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-28518 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-28518?: Check whether you run openviking (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A path traversal vulnerability (Zip Slip) exists in OpenViking's '.ovpack' import mechanism. The software fails to properly validate ZIP archive member names, allowing entries to contain traversal sequences (../), absolute paths, or drive prefixes. An attacker can exploit this by providing a malicious archive to a user; when processed, the application will write files outside the intended destination directory using the privileges of the OpenViking process. This can lead to arbitrary file creation or overwriting of critical system files. The issue is fixed in commit 46b3e76.

Affected products

Volcengine OpenViking <= 0.2.1

Identifiers

CVE-2026-28518
GHSA-rpqr-j937-6qr9
PYSEC-2026-2856

Timeline

2026-02-28: disclosed: Issue reported on GitHub
2026-03-03: advisory: CVE published by VulnCheck/NVD
2026-03-03: patched: Fix commit 46b3e76 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.