Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:HSummary
CVE-2026-22793 is a critical-severity Code Injection (CWE-94) vulnerability in 5Ire 5Ire. Its CVSS base score is 9.6 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked at the 46th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
This vulnerability is AI-related — categorised as LLM Application Platforms; in the LLM/Generative AI Risks risk domain.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-22793 is an unsafe option parsing vulnerability in the ECharts Markdown plugin of 5ire, a cross-platform desktop artificial intelligence assistant and model context protocol client. Versions of 5ire prior to 0.15.3 are affected, enabling attackers to execute arbitrary JavaScript code in the renderer context when malicious ECharts code blocks are submitted. This issue is classified under CWE-94 (Improper Control of Generation of Code) with a CVSS v3.1 base score of 9.6 (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H).
Any user capable of submitting ECharts code blocks—such as through shared documents, chats, or inputs processed by 5ire—can exploit the vulnerability. Successful exploitation allows arbitrary JavaScript execution in the renderer process, potentially escalating to remote code execution (RCE) in Electron-based environments where privileged APIs like electron.mcp are exposed, resulting in full compromise of the host system including high confidentiality, integrity, and availability impacts.
Version 0.15.3 of 5ire patches the vulnerability by addressing the unsafe option parsing. Security practitioners should update to this version immediately. Additional details are available in the GitHub release notes at https://github.com/nanbingxyz/5ire/releases/tag/v0.15.3 and the security advisory at https://github.com/nanbingxyz/5ire/security/advisories/GHSA-wg3x-7c26-97wj.
This vulnerability underscores security risks in AI desktop applications leveraging web rendering components like ECharts and Electron, where user-submitted content can bridge to system-level access. No public evidence of real-world exploitation has been reported as of the CVE publication on 2026-01-21.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-3779
Vulnerability Data
5ire is 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…
more
code in the renderer context. This 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. Version 0.15.3 patches the issue.
- CWE(s)
AI Security AnalysisAI
- AI Category
- LLM Application Platforms
- Risk Domain
- LLM/Generative AI Risks
- OWASP Top 10 for LLMs 2025
- None mapped
- Classification Reason
- Matched keywords: artificial intelligence, mcp, model context protocol
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.3.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation finds code paths that accept and execute externally influenced strings.
Input validation directly stops untrusted data from being used to construct executable code without neutralization.
Least privilege limits the damage an injected code fragment can perform once executed.
Requiring documented secure development standards and tools enforces use of safe code-generation APIs and escaping.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
PR.PS-06's SDLC practices directly target injection flaws via secure coding and testing (mostly), yet as a single broad outcome it leaves many code-generation specifics unaddressed (partial).
PR.DS-10 protects runtime data confidentiality/integrity but has no bearing on neutralizing externally influenced input during code generation, so neither direction shows any preventive effect.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Banning unapproved code samples and unauthenticated web services, combined with secure-coding standards and SAST, prevents the dynamic generation or inclusion of attacker-supplied code.
Controls that restrict unauthorized or malicious code from being introduced via external networks or removable media limit opportunities for an attacker to inject and execute arbitrary code.