# CVE-2026-13507: volcengine OpenViking insufficient verification of data authenticity in VectorDB

Source: https://junglewise.ai/threats/cve-2026-13507-volcengine-openviking-insufficient-verification-of-data  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-28. Updated: 2026-06-28  
License: CC BY 4.0 with a link back

CVE-2026-13507 · Severity: medium · CVSS 5 · Published 2026-06-28

OpenViking is an open-source database used to manage context and memory for AI Agents. A security flaw in how the system identifies data records and generates encryption keys could allow different users or accounts to accidentally share the same data labels or cryptographic keys. In practice, this could lead to data being associated with the wrong account or unauthorized access to sensitive information if an attacker can predict or manipulate record IDs.

## Quick answers

**Is CVE-2026-13507 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-13507 being exploited in the wild.

**How severe is CVE-2026-13507?** Medium severity, with a CVSS score of 5, published 28 June 2026.

**Which products and versions are affected?** volcengine OpenViking up to 0.3.21.

**Is there a fix for CVE-2026-13507?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-13507 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-13507?** Check whether anything you run is named in the advisory. 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 vulnerability exists in OpenViking's Local VectorDB Primary-key Label Handler and cryptographic provider. The function 'str_to_uint64' in 'openviking/storage/vectordb/utils/str_to_uint64.py' generates internal labels by hashing only the record ID, omitting critical security context such as account_id, context_type, or owner_space. Additionally, the HKDF key derivation in 'openviking/crypto/providers.py' fails to include a unique purpose or version parameter. A remote attacker with low privileges could exploit these collisions to cause data rebinding or access keys intended for different logical purposes. A fix has been proposed in pull request #2268 to bind storage and crypto keys to the full security context.

## Affected products

- volcengine OpenViking up to 0.3.21

## Timeline

- 2026-05-27: disclosed: Issue reported on GitHub and pull request submitted
- 2026-06-28: advisory: CVE published via VulDB/NVD

## References

- [https://github.com/volcengine/OpenViking/](https://github.com/volcengine/OpenViking/)
- [https://github.com/volcengine/OpenViking/issues/2263](https://github.com/volcengine/OpenViking/issues/2263)
- [https://github.com/volcengine/OpenViking/pull/2268](https://github.com/volcengine/OpenViking/pull/2268)
- [https://vuldb.com/cve/CVE-2026-13507](https://vuldb.com/cve/CVE-2026-13507)
- [https://vuldb.com/submit/838791](https://vuldb.com/submit/838791)
- [https://vuldb.com/vuln/374515](https://vuldb.com/vuln/374515)
- [https://vuldb.com/vuln/374515/cti](https://vuldb.com/vuln/374515/cti)