5ire
CVE-2025-68669
CRITICAL
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft Mermaid diagram with embedded HTML payload
-
DeliveryDeliver via model output or shared chat
-
ExploitVictim renders diagram in 5ire
-
ExecutionInjected HTML executes in Electron renderer
-
ImpactAchieve arbitrary code execution on host
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that a victim running 5ire version 0.15.2 or earlier renders attacker-controlled Markdown containing a Mermaid diagram; the markdown-it-mermaid plugin in useMarkdown.ts is initialized with securityLevel:'loose', which explicitly permits HTML tags inside Mermaid diagram nodes, so no special non-default setting is needed - the vulnerable configuration ships by default. The principal limiting factor is user interaction (UI:R): the malicious diagram content must actually be displayed/rendered by the victim (e.g., a malicious or prompt-injected model response or a shared conversation), and systems on a fixed release (post-0.15.2 with securityLevel:'strict') are not affected. |
| Impact | The NVD CVSS 3.1 score of 9.6 (Critical) is driven by a network attack vector (AV:N), low complexity (AC:L), no privileges (PR:N), and a scope change (S:C) with full C:H/I:H/A:H impact - consistent with a cross-site-scripting flaw (CWE-79) that escalates to code execution inside an Electron desktop app, where renderer-context HTML injection can reach the Node/OS layer. The one real brake on severity is UI:R: a victim must actually render attacker-supplied Markdown containing a Mermaid diagram, so this is not a wormable, fully unattended network exploit. A publicly available exploit is referenced in the GitHub Security Advisory (GHSA-5hpf-p8fw-j349), which raises practical risk, but there is NO CISA KEV listing and NO EPSS score in the provided data, so 'publicly available exploit code exists' must not be conflated with active exploitation - exploitation status is 'publicly available exploit code exists' only. Net assessment: a genuine high-priority issue for 5ire users because the delivery path (a malicious or prompt-injected AI response, or a shared conversation, rendering untrusted Mermaid/HTML) is realistic for an AI chat client, but overall real-world exposure is constrained by the product's small deployment footprint rather than by exploit difficulty. Note a data conflict: the description states 'not patched at time of publication,' yet commit 1fbe40d0 in the input changes securityLevel from 'loose' to 'strict,' indicating a fix now exists - verify current patched release with the vendor. |
| Exploit ScenarioDerived | An attacker delivers a crafted Mermaid diagram containing embedded HTML/script to a 5ire user - for example via a malicious model response, a prompt-injection that causes the assistant to emit the payload, or a shared conversation. When the victim views the message, useMarkdown.ts renders the diagram with markdown-it-mermaid configured securityLevel:'loose', executing the injected HTML in the app's renderer and, in the Electron desktop context, leading to code execution. A public proof-of-concept is referenced in the GitHub advisory. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 19, 2026
Remote code execution in 5ire 0.15.2 and earlier arises because the desktop AI assistant renders Mermaid diagrams with securityLevel set to 'loose', allowing attacker-supplied HTML/JavaScript embedded in Markdown to execute inside the Electron renderer and potentially reach the host OS. An unauthenticated network attacker can deliver the malicious Markdown through model responses or shared conversations, but exploitation requires the victim to render the content (UI:R). Publicly available exploit code exists; there is no confirmed active exploitation (not in CISA KEV).
RemediationAI
Vendor-released patch: none confirmed; the advisory states the issue was unpatched at publication. Upstream fix available (PR/commit); released patched version not independently confirmed. Apply the fix in commit https://github.com/nanbingxyz/5ire/commit/1fbe40d0bfbfe215370d45b9af856c286d67d3f2, which changes securityLevel from 'loose' to 'strict' in src/hooks/useMarkdown.ts, and track the vendor advisory https://github.com/nanbingxyz/5ire/security/advisories/GHSA-5hpf-p8fw-j349 for a patched release. If upgrading is not immediately possible, disable Mermaid rendering or neutralize/strip Mermaid code blocks before Markdown is rendered; this breaks legitimate diagram display but removes the vulnerable HTML-in-Mermaid path. Restrict 5ire's ability to load untrusted model outputs or shared conversation content, which reduces exposure but may limit intended AI-assistant workflows. Run 5ire under a low-privilege OS account with restricted filesystem and network access, and use Electron hardening such as disabling nodeIntegration and enabling contextIsolation where compatible; these controls limit post-exploitation impact but can affect MCP tool behavior and application functionality.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
5ire is an Electron-based cross-platform desktop AI assistant and Model Context Protocol client. Its Markdown pipeline in src/hooks/useMarkdown.ts initializes the markdown-it-mermaid plugin with securityLevel: 'loose', which explicitly permits HTML tags inside Mermaid diagram nodes rather than sanitizing them under Mermaid's 'strict' mode. When a victim displays attacker-controlled Markdown containing a crafted Mermaid diagram, injected HTML/JavaScript executes in the renderer context; in an Electron desktop application, renderer-context script execution can reach the Node/OS layer depending on process configuration and IPC exposure. This is fundamentally a CWE-79 cross-site scripting flaw whose impact is elevated by the desktop runtime and the scope change in the CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H. The vulnerable configuration ships by default, so no special non-default setting is needed; the primary limiting factor is that the malicious diagram content must actually be rendered. The upstream commit 1fbe40d0bfbfe215370d45b9af856c286d67d3f2 changes securityLevel from 'loose' to 'strict'.
Know when 5ire gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Remotely delivered content requires the victim to render it (UI:R); HTML injection in the renderer escapes to the Electron host (S:C), yielding full code execution and C/I/A:H.
Primary rating from Vendor (github).
CVSS VectorVendor: github
DescriptionCVE.org
5ire is a cross-platform desktop artificial intelligence assistant and model context protocol client. In versions 0.15.2 and prior, an RCE vulnerability exists in useMarkdown.ts, where the markdown-it-mermaid plugin is initialized with securityLevel: 'loose'. This configuration explicitly permits the rendering of HTML tags within Mermaid diagram nodes. This issue has not been patched at time of publication.
Executive ViewAI
5ire desktop AI assistant versions 0.15.2 and earlier can allow attacker-supplied content in Mermaid diagrams to execute code on a user's workstation when rendered, potentially compromising the host operating system. Publicly available exploit code exists, and no vendor patch is available, so employees using affected 5ire installations to view shared or model-generated Markdown remain at risk. Leadership should care because a successful render could expose local data, credentials, and endpoints, and risk must be reduced through product restriction or isolation until remediation is available.
No vendor-released patch identified at time of analysis. Temporarily remove or block 5ire 0.15.2 and earlier on sensitive endpoints; prohibit opening untrusted shared conversations or model-generated Markdown/Mermaid diagrams; run 5ire only in low-privilege, isolated, or virtualized environments; disable Mermaid or Markdown rendering if supported; apply application allow-listing and monitor for suspicious child processes or host activity from the Electron renderer.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Affected Products (CPE)CVE.org
5ire AI assistant desktop application prior to version 0.10.0 has an output encoding vulnerability that allows malicious
5ire MCP client prior to version 0.10.0 has a code injection vulnerability through MCP tool responses that enables arbit
5ire is a cross-platform desktop artificial intelligence assistant and model context protocol client. Rated critical sev
5ire is a cross-platform desktop artificial intelligence assistant and model context protocol client. Rated critical sev
NVD
CVE.org
EPSS
GitHub
Exploit-DB