CVE-2026-64870

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 88% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: Elevated riskExposed: 0

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

MaxKB is an open-source AI assistant for enterprise. In versions 2.0.0 through 2.10.4-lts, UpdateStoreTool.update_tool passes caller-supplied download_url and download_callback_url values to requests.get without equivalent trusted-host and redirect validation, allowing an authenticated workspace user to make the server request internal, loopback, link-local, or cloud metadata URLs. A fix is present on the v2 branch but has not yet been included in a published release.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

July 30, 2026

Last Modified

July 30, 2026

Advisory Details (2)

Auto-updated Jul 30, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit

commit a96a4fc17051 (1Panel-dev/MaxKB)

Fix landed in 1Panel-dev/MaxKB commit a96a4fc17051 — awaiting tagged release

https://github.com/1Panel-dev/MaxKB/commit/a96a4fc17051d80e5b90a632ad8ec851d7d24b58
github Patch Available🟡 PoC Available

UpdateStoreTool fetches caller-supplied app-store URLs without host validation · Advisory · 1Panel-dev/MaxKB · GitHub

https://github.com/1Panel-dev/MaxKB/security/advisories/GHSA-7xxm-gqxv-ph3v

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 52× 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-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 22:31 UTCEG score recompute
  3. 2026-08-28 21:42 UTCEPSS rescore
  4. 2026-08-27 21:22 UTCEG score recompute
  5. 2026-08-26 22:58 UTCEG score recompute
  6. 2026-08-26 14:47 UTCEPSS rescore
  7. 2026-08-26 00:34 UTCEG score recompute
  8. 2026-08-25 13:49 UTCEPSS rescore
  9. 2026-08-25 01:44 UTCEG score recompute
  10. 2026-08-23 04:54 UTCEG score recompute
  11. 2026-08-23 00:19 UTCEPSS rescore
  12. 2026-08-22 06:29 UTCEG score recompute
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 08:05 UTCEG score recompute
  15. 2026-08-20 22:55 UTCEPSS rescore
  16. 2026-08-20 09:41 UTCEG score recompute
  17. 2026-08-19 17:04 UTCEPSS rescore
  18. 2026-08-19 11:16 UTCEG score recompute
  19. 2026-08-18 13:48 UTCEPSS rescore
  20. 2026-08-17 14:09 UTCEG score recompute
  21. 2026-08-17 13:47 UTCEPSS rescore
  22. 2026-08-16 15:45 UTCEG score recompute
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-15 17:21 UTCEG score recompute
  25. 2026-08-15 01:30 UTCEPSS rescore
Show 31 more
  1. 2026-08-14 18:57 UTCEG score recompute
  2. 2026-08-13 22:00 UTCEPSS rescore
  3. 2026-08-12 22:06 UTCEG score recompute
  4. 2026-08-12 13:51 UTCEPSS rescore
  5. 2026-08-11 23:42 UTCEG score recompute
  6. 2026-08-11 01:17 UTCEG score recompute
  7. 2026-08-11 00:00 UTCEPSS rescore
  8. 2026-08-10 02:53 UTCEG score recompute
  9. 2026-08-09 13:47 UTCEPSS rescore
  10. 2026-08-09 04:29 UTCEG score recompute
  11. 2026-08-08 16:37 UTCEPSS rescore
  12. 2026-08-08 06:05 UTCEG score recompute
  13. 2026-08-07 07:41 UTCEG score recompute
  14. 2026-08-06 13:47 UTCEPSS rescore
  15. 2026-08-06 09:17 UTCEG score recompute
  16. 2026-08-05 19:17 UTCEPSS rescore
  17. 2026-08-05 19:17 UTCEPSS rescore
  18. 2026-08-05 10:52 UTCEG score recompute
  19. 2026-08-04 15:10 UTCEPSS rescore
  20. 2026-08-04 12:27 UTCEG score recompute
  21. 2026-08-04 10:39 UTCEPSS rescore
  22. 2026-08-03 13:15 UTCEG score recompute
  23. 2026-08-03 10:36 UTCEPSS rescore
  24. 2026-08-02 14:50 UTCEG score recompute
  25. 2026-08-02 02:27 UTCEPSS rescore
  26. 2026-08-01 16:26 UTCEG score recompute
  27. 2026-08-01 04:16 UTCEPSS rescore
  28. 2026-07-30 19:37 UTCEG score recompute
  29. 2026-07-30 18:02 UTCEG score recompute
  30. 2026-07-30 17:22 UTCEG score recompute
  31. 2026-07-30 17:20 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-64870?
CVE-2026-64870 is a medium vulnerability published on July 30, 2026. MaxKB is an open-source AI assistant for enterprise. In versions 2.0.0 through 2.10.4-lts, UpdateStoreTool.updatetool passes caller-supplied downloadurl and downloadcallbackurl values to requests.get without equivalent trusted-host and redirect validation, allowing an authenticated workspace user…
When was CVE-2026-64870 disclosed?
CVE-2026-64870 was first published in the National Vulnerability Database on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64870 actively exploited?
CVE-2026-64870 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 88.2% of all scored CVEs.
What is the CVSS score of CVE-2026-64870?
CVE-2026-64870 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-64870?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64870, 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-64870

Explore →

Is Your Infrastructure Affected by CVE-2026-64870?

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

Start Free Scan →Browse All CVEs