CVE-2026-79918

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 73% 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
Trending — 3 sources updated this week
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.3Exploit: None knownExposed: 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. Prior to version 2.10.6-lts, the ToolExecutor LD_PRELOAD sandbox hooks execve, execvpe, and execveat to prevent subprocess creation but does not hook fexecve. An authenticated attacker able to execute tool code can call fexecve to start a process outside the sandbox's intended subprocess policy. This issue is fixed in version 2.10.6-lts.

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

Published

September 21, 2026

Last Modified

September 24, 2026

Advisory Details (3)

Auto-updated Sep 21, 2026
Patch available. Sources: github_release, github, github_commit.
github Patch Available

Sandbox escape via unhooked fexecve · Advisory · 1Panel-dev/MaxKB · GitHub

https://github.com/1Panel-dev/MaxKB/security/advisories/GHSA-9mh9-v949-fwqh
github_release Patch Available

Release v2.10.6-lts (1Panel-dev/MaxKB)

Patch available: 1Panel-dev/MaxKB v2.10.6-lts

https://github.com/1Panel-dev/MaxKB/releases/tag/v2.10.6-lts
github_commit Patch Available

commit 6fa7947a8503 (1Panel-dev/MaxKB)

Patch available: 1Panel-dev/MaxKB v2.10.6-lts (contains commit 6fa7947a8503)

https://github.com/1Panel-dev/MaxKB/commit/6fa7947a85030b87977c4026f33af11ca10dd1e6

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 11× 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-09-24 23:37 UTCEG score recompute
  2. 2026-09-24 22:52 UTCEG score recompute
  3. 2026-09-24 16:39 UTCEG score recompute
  4. 2026-09-24 14:04 UTCEPSS rescore
  5. 2026-09-23 18:08 UTCEG score recompute
  6. 2026-09-23 17:54 UTCEPSS rescore
  7. 2026-09-22 19:45 UTCEG score recompute
  8. 2026-09-22 16:01 UTCEPSS rescore
  9. 2026-09-21 21:22 UTCEG score recompute
  10. 2026-09-21 20:58 UTCEG score recompute
  11. 2026-09-21 20:57 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-79918?
CVE-2026-79918 is a medium vulnerability published on September 21, 2026. MaxKB is an open-source AI assistant for enterprise. Prior to version 2.10.6-lts, the ToolExecutor LD_PRELOAD sandbox hooks execve, execvpe, and execveat to prevent subprocess creation but does not hook fexecve. An authenticated attacker able to execute tool code can call fexecve to start a process…
When was CVE-2026-79918 disclosed?
CVE-2026-79918 was first published in the National Vulnerability Database on September 21, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-79918 actively exploited?
CVE-2026-79918 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 72.7% of all scored CVEs.
What is the CVSS score of CVE-2026-79918?
CVE-2026-79918 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-79918?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-79918, 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-79918

Explore →

Is Your Infrastructure Affected by CVE-2026-79918?

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

Book a Demo →Browse All CVEs