MyScale MyScaleDB up to 1.8.0 SegmentId.h SegmentId::getCacheKey data authenticity
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 2.10- |
Summary
A vulnerability was found in MyScale MyScaleDB up to 1.8.0. It has been rated as problematic. This issue affects the function SegmentId::getCacheKey in the library src/VectorIndex/Common/SegmentId.h. This manipulation causes data authenticity.
This vulnerability is handled as CVE-2026-13513. The attack can be initiated remotely. Additionally, an exploit exists.
The pull request to fix this issue awaits acceptance.
Details
A vulnerability has been found in MyScale MyScaleDB up to 1.8.0 and classified as problematic. Affected by this vulnerability is the function SegmentId::getCacheKey in the library src/VectorIndex/Common/SegmentId.h. The manipulation 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.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-13513. The exploitation appears to be difficult. The attack can be launched remotely. Technical details and also a public exploit are known.
It is possible to download the exploit at github.com. It is declared as proof-of-concept. 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.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 4.6
VulDB Base Score: 5.0
VulDB Temp Score: 4.6
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: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
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: 54
Status: Not defined
Confirmation: 🔒
CVE: CVE-2026-13513 (🔒)
GCVE (CVE): GCVE-0-2026-13513
GCVE (VulDB): GCVE-100-374521
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 06/28/2026 08:38Changes: 06/28/2026 08:38 (58)
Complete: 🔍
Submitter: Dem000000
Cache ID: 216::103
Submit
Accepted
- Submit #838878: MyScale MyScaleDB 1.8.0 source tree at commit 20a16d32; likely affected where the same vector-index mutation/cache code is present CWE-345 Insufficient Verification of Data Authenticity (by Dem000000)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.