CVE-2026-6108

MEDIUMNVD 6.36.3
EchelonGraph scoreMEDIUM confidence

Score 6.3 from GitHub Security Advisory published 2026-04-12. NVD baseline CVSS 6.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 6.3Exploit: Elevated riskExposed: 0

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

A vulnerability was found in 1Panel-dev MaxKB up to 2.6.1. The affected element is the function execute of the file apps/application/flow/step_node/mcp_node/impl/base_mcp_node.py of the component Model Context Protocol Node. Performing a manipulation results in os command injection. The attack is possible to be carried out remotely. The exploit has been made public and could be used. You should upgrade the affected component. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.

CVSS v3
6.3
EG Score
6.3(medium)
EG Risk
44(Track)
EG Risk 44/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
Severity63% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
72%
KEV
Not listed

Published

April 12, 2026

Last Modified

April 29, 2026

Advisory Details (1)

Auto-updated Aug 2, 2026
No patch confirmed yet.
generic

Remote Code Execution in MaxKB via MCP Server Configuration Validation Bypass · Issue #30 · AnalogyC0de/public_exp · GitHub

https://github.com/AnalogyC0de/public_exp/issues/30

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 3× in last 7d / 24× 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.

Showing the most recent 100 of 168 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-6108?
CVE-2026-6108 is a medium vulnerability published on April 12, 2026. A vulnerability was found in 1Panel-dev MaxKB up to 2.6.1. The affected element is the function execute of the file apps/application/flow/stepnode/mcpnode/impl/basemcpnode.py of the component Model Context Protocol Node. Performing a manipulation results in os command injection. The attack is…
When was CVE-2026-6108 disclosed?
CVE-2026-6108 was first published in the National Vulnerability Database on April 12, 2026, with the most recent update on April 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-6108 actively exploited?
CVE-2026-6108 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 28.1% of all scored CVEs.
What is the CVSS score of CVE-2026-6108?
CVE-2026-6108 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-6108?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6108, 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-6108

Explore →

Is Your Infrastructure Affected by CVE-2026-6108?

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