CVE-2026-22793: 5ire Desktop AI Assistant RCE Vulnerability

CVE-2026-22793 Overview

CVE-2026-22793 is a Code Injection vulnerability affecting 5ire, a cross-platform desktop artificial intelligence assistant and model context protocol client. Prior to version 0.15.3, an unsafe option parsing vulnerability in the ECharts Markdown plugin allows any user able to submit ECharts code blocks to execute arbitrary JavaScript code in the renderer context. This vulnerability can lead to Remote Code Execution (RCE) in environments where privileged APIs (such as Electron's electron.mcp) are exposed, resulting in full compromise of the host system.

Critical Impact

This vulnerability enables arbitrary JavaScript execution in the Electron renderer context, potentially allowing attackers to leverage privileged APIs for complete host system compromise through crafted ECharts code blocks.

Affected Products

• 5ire desktop application versions prior to 0.15.3
• Systems running 5ire with ECharts Markdown plugin enabled
• Electron-based deployments exposing privileged APIs like electron.mcp

Discovery Timeline

• 2026-01-21 - CVE CVE-2026-22793 published to NVD
• 2026-01-21 - Last updated in NVD database

Technical Details for CVE-2026-22793

Vulnerability Analysis

This vulnerability stems from CWE-94 (Improper Control of Generation of Code - Code Injection). The ECharts Markdown plugin in 5ire fails to properly sanitize or validate options passed through ECharts code blocks before processing them. This allows attackers to inject arbitrary JavaScript code that executes within the Electron renderer context.

In Electron applications, the renderer process can have access to privileged Node.js APIs when certain security configurations are relaxed. When the electron.mcp API or similar privileged interfaces are exposed to the renderer, code execution within this context can escalate to full system access, enabling attackers to read/write files, execute system commands, and interact with the operating system at the user's privilege level.

The network-based attack vector requires user interaction—typically convincing a user to render a malicious ECharts code block within the 5ire application. The scope change indicated by the vulnerability metrics reflects that exploitation in the renderer context can affect resources beyond the vulnerable component, specifically the underlying host system.

Root Cause

The root cause is inadequate input validation and sanitization in the ECharts Markdown plugin's option parsing logic. The plugin processes user-supplied ECharts configuration objects without properly restricting or escaping JavaScript code that can be embedded within these options. ECharts supports various callback functions and event handlers in its configuration objects, and the plugin failed to properly neutralize these execution paths before rendering.

Attack Vector

The attack leverages the network-based attack surface where a malicious actor crafts a specially formatted ECharts code block containing JavaScript payloads within the chart configuration options. When a 5ire user processes or renders content containing this malicious code block, the injected JavaScript executes in the renderer context.

The exploitation scenario involves:

1. Attacker crafts an ECharts code block with embedded JavaScript in configuration callbacks or event handlers
2. The malicious content is delivered to a victim through any mechanism that allows content submission (chat, shared documents, imported files)
3. When 5ire renders the ECharts visualization, the unsafe option parsing executes the embedded JavaScript
4. If privileged APIs like electron.mcp are accessible, the attacker gains the ability to execute arbitrary code on the host system

For technical details on the vulnerability mechanism, refer to the GitHub Security Advisory GHSA-wg3x-7c26-97wj.

Detection Methods for CVE-2026-22793

Indicators of Compromise

• Unexpected JavaScript execution patterns in Electron renderer logs
• Unusual process spawning from the 5ire application
• System command execution originating from the 5ire process
• Network connections to unknown destinations initiated by 5ire
• File system modifications in unexpected locations by the 5ire process

Detection Strategies

• Monitor Electron application logs for JavaScript errors or execution anomalies in ECharts rendering contexts
• Implement application-level logging to track content rendering events, particularly ECharts code blocks
• Deploy endpoint detection and response (EDR) solutions to identify suspicious child process creation from desktop applications
• Audit content sources for potentially malicious ECharts configurations

Monitoring Recommendations

• Enable verbose logging for the 5ire application to capture rendering events
• Configure SentinelOne to monitor for suspicious behavior from Electron-based applications
• Implement network monitoring to detect unusual outbound connections from desktop AI assistants
• Review imported content and shared documents for suspicious ECharts code blocks

How to Mitigate CVE-2026-22793

Immediate Actions Required

• Upgrade 5ire to version 0.15.3 or later immediately
• Audit any content rendered through 5ire for potentially malicious ECharts code blocks
• Restrict access to untrusted content sources until patching is complete
• Review system logs for any indicators of compromise

Patch Information

The vulnerability has been patched in 5ire version 0.15.3. Users should update to this version or later to remediate the vulnerability. The fix implements proper sanitization of ECharts options to prevent arbitrary JavaScript execution.

For detailed patch information, see the GitHub Release v0.15.3.

Workarounds

• Disable or remove the ECharts Markdown plugin until the patch can be applied
• Avoid rendering content from untrusted sources in 5ire
• Implement content security policies to restrict script execution where possible
• Run 5ire with minimal system privileges to limit the impact of potential exploitation

# Verify current 5ire version and update
# Check installed version
5ire --version

# Update to patched version 0.15.3 or later
# Follow platform-specific update procedures from the official repository
# https://github.com/nanbingxyz/5ire/releases/tag/v0.15.3