CVE-2026-13513

MEDIUMPre-NVD 5.05.0—
EchelonGraph scoreHIGH confidence

Score 5.0 from GitHub Security Advisory (severity: LOW) published 2026-06-29. a secondary CVSS source baseline 5.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
5.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.0
EG Score
5.0(high)
EPSS
3.2%
KEV
Not listed

Published

June 28, 2026

Last Modified

June 29, 2026

Advisory Details (3)

Auto-updated Jun 29, 2026
No patch confirmed yet. Sources: github_pr.
generic

GitHub - myscale/MyScaleDB: A @ClickHouse fork that supports high-performance vector search and full-text search. · GitHub

https://github.com/myscale/MyScaleDB/
github_pr

Fix vector index reuse after indexed column update

Upstream fix in progress (PR #55 · myscale/MyScaleDB, state=open)

https://github.com/myscale/MyScaleDB/pull/55
generic

Vector index is reused after ALTER UPDATE changes the indexed vector column · Issue #54 · myscale/MyScaleDB · GitHub

https://github.com/myscale/MyScaleDB/issues/54

Vendor Advisories for CVE-2026-13513(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 19× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 11:01 UTCEG score recompute
  2. 2026-07-06 11:00 UTCGHSA enrichment
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-05 12:28 UTCEG score recompute
  5. 2026-07-05 12:28 UTCGHSA enrichment
  6. 2026-07-04 14:02 UTCEG score recompute
  7. 2026-07-04 14:02 UTCGHSA enrichment
  8. 2026-07-04 06:31 UTCEPSS rescore
  9. 2026-07-03 15:36 UTCEG score recompute
  10. 2026-07-03 15:35 UTCGHSA enrichment
  11. 2026-07-02 17:11 UTCEG score recompute
  12. 2026-07-02 17:11 UTCGHSA enrichment
  13. 2026-07-01 18:45 UTCEG score recompute
  14. 2026-07-01 18:45 UTCGHSA enrichment
  15. 2026-07-01 15:06 UTCEPSS rescore
  16. 2026-07-01 15:06 UTCEPSS rescore
  17. 2026-06-30 23:22 UTCEPSS rescore
  18. 2026-06-30 20:21 UTCEG score recompute
  19. 2026-06-30 20:21 UTCGHSA enrichment
  20. 2026-06-29 21:57 UTCEG score recompute
  21. 2026-06-29 21:57 UTCGHSA enrichment
  22. 2026-06-29 14:06 UTCEPSS rescore
  23. 2026-06-29 14:04 UTCNVD updateCVSS v4 → 1.3
  24. 2026-06-29 12:02 UTCMITRE cvelistV5CVSS v4 → 2.3
  25. 2026-06-29 02:03 UTCNVD updateCVSS v4 → 1.3
Show 2 more
  1. 2026-06-28 23:33 UTCEG score recompute
  2. 2026-06-28 23:32 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-13513?
CVE-2026-13513 is a medium vulnerability published on June 28, 2026. 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…
When was CVE-2026-13513 disclosed?
CVE-2026-13513 was first published in the National Vulnerability Database on June 28, 2026, with the most recent update on June 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13513 actively exploited?
CVE-2026-13513 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-13513?
CVE-2026-13513 has a CVSS v3 base score of 5.0 (NVD).
How do I remediate CVE-2026-13513?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13513, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-13513

Explore →

Is Your Infrastructure Affected by CVE-2026-13513?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs