Cross-context record collision via bare-ID hashing
Published Jun 28, 2026 · Updated Jun 28, 2026
Data authenticity failure in OpenViking 0.3.0 through 0.3.21 allows remote authenticated users to collide local VectorDB record identities. str_to_uint64 hashes a caller-provided bare ID without its account, URI, or other security context, so equal IDs map to one label in the shared collection. Reachability requires an authenticated path that supplies IDs to the low-level storage API; higher-level embedding code normally namespaces IDs by account and URI.
Summary
What happened
Data authenticity failure in OpenViking 0.3.0 through 0.3.21 allows remote authenticated users to collide local VectorDB record identities. str_to_uint64 hashes a caller-provided bare ID without its account, URI, or other security context, so equal IDs map to one label in the shared collection. Reachability requires an authenticated path that supplies IDs to the low-level storage API; higher-level embedding code normally namespaces IDs by account and URI.
The record
- CVE
- CVE-2026-13507
- Published
- Jun 28, 2026
- Updated
- Jun 28, 2026
- Vendor
- Volcengine
- Product
- OpenViking
- Classifications
- CWE-345, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 28, 2026CVE publishedPublication date reported by the CVE source.
- Jun 28, 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.3.0
- Affected versionversion=0.3.1
- Affected versionversion=0.3.10
- Affected versionversion=0.3.11
- Affected versionversion=0.3.12
- Affected versionversion=0.3.13
- Affected versionversion=0.3.14
- Affected versionversion=0.3.15
- Affected versionversion=0.3.16
- Affected versionversion=0.3.17
- Affected versionversion=0.3.18
- Affected versionversion=0.3.19
- Affected versionversion=0.3.2
- Affected versionversion=0.3.20
- Affected versionversion=0.3.21
- Affected versionversion=0.3.3
- Affected versionversion=0.3.4
- Affected versionversion=0.3.5
- Affected versionversion=0.3.6
- Affected versionversion=0.3.7
- Affected versionversion=0.3.8
- Affected versionversion=0.3.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Bare-ID VectorDB label collision reproducerproof 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