Insufficient Data Authenticity Verification in MyScale MyScaleDB
CVE-2026-13513

2.3LOW

Key Information:

Vendor

Myscale

Status
Myscaledb
Vendor
CVE Published:
28 June 2026

Badges

👾 Exploit Exists🟡 Public PoC

What is CVE-2026-13513?

A security flaw has been identified in MyScaleDB, specifically in the SegmentId::getCacheKey function within the src/VectorIndex/Common/SegmentId.h library. This vulnerability leads to insufficient verification of data authenticity, allowing remote attackers to potentially exploit affected systems. The complexity required to exploit this flaw is considerably high, making it a challenge to successfully execute an attack. A patch has been proposed and is currently awaiting acceptance, emphasizing the need for users to stay informed and secure their installations against potential threats.

Affected Version(s)

MyScaleDB 1.0

MyScaleDB 1.1

MyScaleDB 1.2

Exploit Proof of Concept (PoC)

PoC code is written by security researchers to demonstrate the vulnerability can be exploited. PoC code is also a key component for weaponization which could lead to ransomware.

CVE-2026-13513 - Proof of Concept

References

https://vuldb.com/vuln/374521
vdb-entrytechnical-description
https://vuldb.com/vuln/374521/cti
signaturepermissions-required
https://vuldb.com/cve/CVE-2026-13513
third-party-advisory

CVSS V4

Score:
2.3
Severity:
LOW
Confidentiality:
Low
Integrity:
Low
Availability:
Low
Attack Vector:
Network
Attack Complexity:
High
Attack Required:
None
Privileges Required:
Undefined
User Interaction:
None

Timeline

  • 🟡

    Public PoC available

  • 👾

    Exploit known to exist

  • Vulnerability published

  • Vulnerability Reserved

Credit

Dem000000 (VulDB User)
VulDB CNA Team
.