Arbitrary file write via unvalidated ZIP paths
Published Mar 3, 2026 · Updated Mar 3, 2026
Path traversal in OpenViking 0.2.1 and earlier allows attackers to write files outside the import directory through a crafted .ovpack. The import_ovpack routine passes unvalidated ZIP member names into relative-path and file-write operations, accepting traversal segments, absolute paths, and drive prefixes. A user must import the malicious archive; resulting writes run with the importing process's privileges and can create or overwrite accessible files.
Summary
What happened
Path traversal in OpenViking 0.2.1 and earlier allows attackers to write files outside the import directory through a crafted .ovpack. The import_ovpack routine passes unvalidated ZIP member names into relative-path and file-write operations, accepting traversal segments, absolute paths, and drive prefixes. A user must import the malicious archive; resulting writes run with the importing process's privileges and can create or overwrite accessible files.
The record
- CVE
- CVE-2026-28518
- Published
- Mar 3, 2026
- Updated
- Mar 3, 2026
- Vendor
- Volcengine
- Product
- OpenViking
- Classifications
- CWE-22, T1565.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 3, 2026CVE publishedPublication date reported by the CVE source.
- Mar 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=0.2.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- OpenViking issue 342 minimal reproducible exampleproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo