volcengine OpenViking up to 0.3.21 Local VectorDB Primary-key Label str_to_uint64.py str_to_uint64 ID data authenticity
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 2.79 |
Summary
A vulnerability, which was classified as problematic, has been found in volcengine OpenViking up to 0.3.21. This impacts the function str_to_uint64 of the file openviking/storage/vectordb/utils/str_to_uint64.py of the component Local VectorDB Primary-key Label Handler. This manipulation of the argument ID causes data authenticity.
This vulnerability is registered as CVE-2026-13507. Remote exploitation of the attack is possible. No exploit is available.
The pull request to fix this issue awaits acceptance.
Details
A vulnerability was found in volcengine OpenViking up to 0.3.21. It has been declared as problematic. Affected by this vulnerability is the function str_to_uint64 of the file openviking/storage/vectordb/utils/str_to_uint64.py of the component Local VectorDB Primary-key Label Handler. The manipulation of the argument id with an unknown input leads to a data authenticity vulnerability. The CWE definition for the vulnerability is CWE-345. The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. As an impact it is known to affect confidentiality, integrity, and availability.
It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-13507. The exploitation appears to be difficult. The attack can be launched remotely. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/28/2026).
The pull request to fix this issue awaits acceptance.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
- 0.3.0
- 0.3.1
- 0.3.2
- 0.3.3
- 0.3.4
- 0.3.5
- 0.3.6
- 0.3.7
- 0.3.8
- 0.3.9
- 0.3.10
- 0.3.11
- 0.3.12
- 0.3.13
- 0.3.14
- 0.3.15
- 0.3.16
- 0.3.17
- 0.3.18
- 0.3.19
- 0.3.20
- 0.3.21
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.0
VulDB Temp Score: 4.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Data authenticityCWE: CWE-345
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
06/28/2026 Advisory disclosed06/28/2026 VulDB entry created
06/28/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 2263
Status: Not defined
Confirmation: 🔒
CVE: CVE-2026-13507 (🔒)
GCVE (CVE): GCVE-0-2026-13507
GCVE (VulDB): GCVE-100-374515
Entry
Created: 06/28/2026 08:23Changes: 06/28/2026 08:23 (57)
Complete: 🔍
Submitter: Dem000000
Cache ID: 216::103
Submit
Accepted
- Submit #838791: ByteDance / Volcengine OpenViking Commit 55a0c0ea15d55dca231fc3a1654474032478bcd8 (2026-03-25); affected released versions unknown CWE-345 Insufficient Verification of Data Authenticity (by Dem000000)
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.