CVE-2026-10813

LOWPre-NVD 3.63.6—
EchelonGraph scoreMEDIUM confidence

Score 3.6 from GitHub Security Advisory (severity: LOW) published 2026-06-04. the CNA's CVSS baseline 3.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vuldb, epss, ghsa
Elevated
3.6
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 3.6Exploit: NoneExposed: 0

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

A flaw has been found in LMCache up to 0.4.6. This affects the function hex_hash_to_int16 of the file lmcache/integration/vllm/utils.py of the component KV Cache Handler. Executing a manipulation can lead to use of weak hash. The attack needs to be launched locally. The attack requires a high level of complexity. It is indicated that the exploitability is difficult. The exploit has been published and may be used. The pull request to fix this issue awaits acceptance.

CVSS v3
3.6
EG Score
3.6(medium)
EPSS
0.1%
KEV
Not listed

Published

June 4, 2026

Last Modified

July 22, 2026

References (7)

Vendor Advisories for CVE-2026-10813(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 28× 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-22 20:52 UTCNVD updateCVSS v4 → 1.1
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-19 14:30 UTCEPSS rescore
  4. 2026-07-18 10:04 UTCEPSS rescore
  5. 2026-07-16 17:02 UTCEPSS rescore
  6. 2026-07-14 21:29 UTCGHSA enrichment
  7. 2026-07-13 22:30 UTCEPSS rescore
  8. 2026-07-13 06:12 UTCEPSS rescore
  9. 2026-07-12 05:46 UTCEPSS rescore
  10. 2026-07-11 14:51 UTCGHSA enrichment
  11. 2026-07-09 19:10 UTCEPSS rescore
  12. 2026-07-08 15:15 UTCEPSS rescore
  13. 2026-07-08 15:15 UTCEPSS rescore
  14. 2026-07-08 09:42 UTCGHSA enrichment
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-05 02:30 UTCEPSS rescore
  18. 2026-07-03 02:14 UTCGHSA enrichment
  19. 2026-07-01 15:06 UTCEPSS rescore
  20. 2026-07-01 15:06 UTCEPSS rescore
  21. 2026-06-30 23:22 UTCEPSS rescore
  22. 2026-06-29 20:01 UTCGHSA enrichment
  23. 2026-06-27 03:08 UTCEPSS rescore
  24. 2026-06-26 14:56 UTCGHSA enrichment
  25. 2026-06-25 13:49 UTCEPSS rescore
Show 31 more
  1. 2026-06-24 14:05 UTCEPSS rescore
  2. 2026-06-23 21:32 UTCEPSS rescore
  3. 2026-06-23 02:17 UTCGHSA enrichment
  4. 2026-06-22 14:25 UTCEPSS rescore
  5. 2026-06-22 14:25 UTCEPSS rescore
  6. 2026-06-21 14:56 UTCEPSS rescore
  7. 2026-06-21 14:56 UTCEPSS rescore
  8. 2026-06-21 01:59 UTCEPSS rescore
  9. 2026-06-21 01:59 UTCEPSS rescore
  10. 2026-06-19 19:25 UTCEPSS rescore
  11. 2026-06-18 17:52 UTCEPSS rescore
  12. 2026-06-17 17:53 UTCEPSS rescore
  13. 2026-06-17 12:02 UTCGHSA enrichment
  14. 2026-06-15 17:48 UTCEPSS rescore
  15. 2026-06-14 23:18 UTCEPSS rescore
  16. 2026-06-14 06:56 UTCGHSA enrichment
  17. 2026-06-12 23:12 UTCEPSS rescore
  18. 2026-06-11 14:00 UTCEPSS rescore
  19. 2026-06-11 01:49 UTCGHSA enrichment
  20. 2026-06-10 22:18 UTCEPSS rescore
  21. 2026-06-10 13:22 UTCEPSS rescore
  22. 2026-06-08 14:17 UTCEPSS rescore
  23. 2026-06-08 14:17 UTCEPSS rescore
  24. 2026-06-07 20:45 UTCGHSA enrichment
  25. 2026-06-07 15:25 UTCEPSS rescore
  26. 2026-06-07 15:24 UTCEPSS rescore
  27. 2026-06-06 13:47 UTCEPSS rescore
  28. 2026-06-06 13:47 UTCEPSS rescore
  29. 2026-06-06 13:47 UTCEPSS rescore
  30. 2026-06-05 22:47 UTCEPSS rescore
  31. 2026-06-04 15:40 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-10813?
CVE-2026-10813 is a low vulnerability published on June 4, 2026. A flaw has been found in LMCache up to 0.4.6. This affects the function hexhashto_int16 of the file lmcache/integration/vllm/utils.py of the component KV Cache Handler. Executing a manipulation can lead to use of weak hash. The attack needs to be launched locally. The attack requires a high level…
When was CVE-2026-10813 disclosed?
CVE-2026-10813 was first published in the National Vulnerability Database on June 4, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10813 actively exploited?
CVE-2026-10813 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-10813?
CVE-2026-10813 has a CVSS v3 base score of 3.6 (NVD).
How do I remediate CVE-2026-10813?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10813, 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-10813

Explore →

Is Your Infrastructure Affected by CVE-2026-10813?

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

Start Free Scan →Browse All CVEs