Vulnerability · Published Jun 28, 2026 · Assigned by VulDB

CVE-2026-13513MyScale MyScaleDB SegmentId.h getCacheKey data authenticity

Medium 5.0

In plain English

A medium-severity insufficient verification of data authenticity in MyScaleDB from MyScale. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 8% of all known vulnerabilities).

Severity (CVSS 3.1)5.0Medium

Exploit odds (30 days)0.2%top 92.4% of all CVEs

Exploited in the wildNo reportsCISA SSVC: poc

Attack toolingNoneno public tooling known

Official description

A security flaw has been discovered in MyScale MyScaleDB up to 1.8.0. This vulnerability affects the function SegmentId::getCacheKey in the library src/VectorIndex/Common/SegmentId.h. The manipulation results in insufficient verification of data authenticity. It is possible to launch the attack remotely. A high complexity level is associated with this attack. It is stated that the exploitability is difficult. The exploit has been released to the public and may be used for attacks. The pull request to fix this issue awaits acceptance.

Affected products (as reported)

Vendor	Product	Versions
MyScale	MyScaleDB	1.01.11.21.31.41.51.61.7

Weakness: CWE-345 · Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R

References

VDB-374521 | MyScale MyScaleDB SegmentId.h getCacheKey data authenticity vdb-entry, technical-description
VDB-374521 | CTI Indicators (IOB, IOC, IOA) signature, permissions-required
CVE-2026-13513 | CVE Analysis and Report third-party-advisory
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 third-party-advisory
https://github.com/myscale/MyScaleDB/issues/54 exploit, issue-tracking
https://github.com/myscale/MyScaleDB/pull/55 issue-tracking, patch
https://github.com/myscale/MyScaleDB/ product