Skip to main content
VulnerabilityPublished

CVE-2026-22793: nanbingxyz 5ire · Code Injection

Affects nanbingxyz 5ireSource CVE Database V5

0

Not known to be exploited · CVSS 9.7 Critical : upgrade to 0.15.3 as a priority.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.7Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.15.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade 5ire and nanbingxyz/5ire to 0.15.3.

Affected software

ProductAffectedFixed in
nanbingxyz5ireAffected
  • <0.15.3
Fixed in
  • 0.15.3
GitHubnanbingxyz/5irepkg:github/nanbingxyz/5ireOther threatsAffected
  • <0.15.3
Fixed in
  • 0.15.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediately upgrade all instances of nanbingxyz 5ire to version 0.15.3 or later, which contains the patch for this vulnerability.
  2. Restrict the ability of untrusted users to submit or render ECharts code blocks within 5ire, implementing strict input validation and sanitization.
  3. Review and minimize exposure of privileged Electron APIs such as electron.mcp in the renderer context; consider applying context isolation and disabling Node.js integration where possible.
  4. Employ application-level sandboxing and use Electron’s security best practices, including enabling Content Security Policy (CSP) to restrict script execution.
  5. Monitor logs and network traffic for suspicious activity related to ECharts rendering or unexpected JavaScript execution.
  6. Educate users about the risks of interacting with untrusted content within 5ire and implement phishing awareness training.
  7. For organizations with custom deployments, conduct code audits to ensure no other plugins or components allow unsafe code execution.
  8. Maintain up-to-date backups and incident response plans in case of compromise.

Description

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 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.

References

Community reviews

Loading reviews…