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

> Attackers can bypass data authenticity checks in MyScaleDB's cache key generation, potentially compromising data integrity or confidentiality.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jun 2026
- **Updated:** 29 Jun 2026
- **Also known as:** GHSA-q6r3-vph9-qrqg

## What is CVE-2026-13513?

CVE-2026-13513 is a low-severity vulnerability in MyScaleDB, published on 28 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### 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.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-13513?


## How do I fix CVE-2026-13513?

No fix has been published for CVE-2026-13513 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-13513 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-13513 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-13513 and fix it if it is affected.

What it is: CVE-2026-13513 is a low-severity vulnerability in MyScaleDB, published on 28 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-13513 exists.

Affected product: MyScaleDB. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-13513/ (Markdown: https://insights.sbomify.com/CVE-2026-13513/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-13513
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-13513
- OSV: https://osv.dev/vulnerability/CVE-2026-13513

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-13513/
Summaries are generated and may contain mistakes; the official description above is the record.