CVE-2026-13513
MyScale MyScaleDB SegmentId.h getCacheKey data authenticity
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.
INFO
Published Date :
June 28, 2026, 11 p.m.
Last Modified :
June 28, 2026, 11 p.m.
Remotely Exploit :
No
Source :
VulDB
Affected Products
The following products are affected by CVE-2026-13513
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Review and accept the pull request for the fix.
- Update MyScaleDB to a patched version.
- Verify segment ID cache key verification.
- Monitor for exploitation attempts.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-13513 vulnerability anywhere in the article.