CVE-2026-64870

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (28th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
5.3EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.3Exploit: No code on recordExposed services: Not assessed

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

The CVE record's description, written by its CNA (GitHub, Inc.), states the affected versions: "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…" No release containing a fix is confirmed on record.

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.3MEDIUMmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix.
EPSS PROB
0.4%
EPSS %ILE
28th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 30, 2026

Last Modified

July 30, 2026

Advisory Details (2)

Auto-updated Jul 30, 2026
No fix on record yet. 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 advisoryMentions a patch (unverified)

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 8× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 126 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 26 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  2. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  3. 2026-10-18 03:22 UTCEG score recompute
  4. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  5. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  6. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  7. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  8. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  9. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  10. 2026-10-12 15:47 UTCEG score recompute
  11. 2026-10-11 19:32 UTCEG score recompute
  12. 2026-10-11 16:47 UTCEG score recompute
  13. 2026-10-11 14:08 UTCEG score recompute
  14. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  15. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  16. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  17. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  18. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  19. 2026-10-06 23:52 UTCEG score recompute
  20. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  21. 2026-10-05 19:59 UTCEG score recompute
  22. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  23. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  24. 2026-10-04 06:37 UTCEG score recompute
  25. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 27th percentile
Show 75 more
  1. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  2. 2026-10-02 16:56 UTCEG score recompute
  3. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  4. 2026-10-01 02:53 UTCEG score recompute
  5. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  6. 2026-09-29 06:53 UTCEG score recompute
  7. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  8. 2026-09-27 19:00 UTCEG score recompute
  9. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  10. 2026-09-25 04:56 UTCEG score recompute
  11. 2026-09-23 21:29 UTCEG score recompute
  12. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  13. 2026-09-22 15:12 UTCEG score recompute
  14. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  15. 2026-09-20 03:41 UTCEG score recompute
  16. 2026-09-19 04:15 UTCEG score recompute
  17. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  18. 2026-09-18 02:23 UTCEG score recompute
  19. 2026-09-17 03:57 UTCEG score recompute
  20. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  21. 2026-09-16 05:33 UTCEG score recompute
  22. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  23. 2026-09-15 03:15 UTCEG score recompute
  24. 2026-09-14 00:12 UTCEG score recompute
  25. 2026-09-13 01:46 UTCEG score recompute
  26. 2026-09-12 03:21 UTCEG score recompute
  27. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  28. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  29. 2026-09-11 04:57 UTCEG score recompute
  30. 2026-09-09 07:11 UTCEG score recompute
  31. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  32. 2026-09-07 19:49 UTCEG score recompute
  33. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  34. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  35. 2026-09-06 08:21 UTCEG score recompute
  36. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  37. 2026-09-05 09:51 UTCEG score recompute
  38. 2026-09-04 11:26 UTCEG score recompute
  39. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  40. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  41. 2026-09-01 22:37 UTCEG score recompute
  42. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  43. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  44. 2026-08-30 20:57 UTCEG score recompute
  45. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  46. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  47. 2026-08-29 22:31 UTCEG score recompute
  48. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  49. 2026-08-27 21:22 UTCEG score recompute
  50. 2026-08-26 22:58 UTCEG score recompute
  51. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  52. 2026-08-26 00:34 UTCEG score recompute
  53. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  54. 2026-08-25 01:44 UTCEG score recompute
  55. 2026-08-23 04:54 UTCEG score recompute
  56. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  57. 2026-08-22 06:29 UTCEG score recompute
  58. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  59. 2026-08-21 08:05 UTCEG score recompute
  60. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  61. 2026-08-20 09:41 UTCEG score recompute
  62. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  63. 2026-08-19 11:16 UTCEG score recompute
  64. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  65. 2026-08-17 14:09 UTCEG score recompute
  66. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  67. 2026-08-16 15:45 UTCEG score recompute
  68. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  69. 2026-08-15 17:21 UTCEG score recompute
  70. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  71. 2026-08-14 18:57 UTCEG score recompute
  72. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  73. 2026-08-12 22:06 UTCEG score recompute
  74. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  75. 2026-08-11 23:42 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-64870?
CVE-2026-64870 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-64870 published?
The CVE record for CVE-2026-64870 was published on July 30, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 30, 2026; the record at its source may have been updated since.
Is CVE-2026-64870 actively exploited?
CVE-2026-64870 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-64870?
CVE-2026-64870 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-64870?
No fix for CVE-2026-64870 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix. The CVE record's description, written by its CNA (GitHub, Inc.), states the affected versions: "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…" No release containing a fix is confirmed on record.

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.

Book a Demo →Browse All CVEs