{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22793 exists.","fix":"No fix has been published for CVE-2026-22793 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-22793 is a critical code injection vulnerability in nanbingxyz 5ire, published on 21 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-22793 and fix it if it is affected.\n\nWhat it is: CVE-2026-22793 is a critical code injection vulnerability in nanbingxyz 5ire, published on 21 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22793 exists.\n\nAffected product: nanbingxyz 5ire. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-22793/ (Markdown: https://insights.sbomify.com/CVE-2026-22793/index.md)","id":"CVE-2026-22793","markdown":"https://insights.sbomify.com/CVE-2026-22793/index.md","name":"CVE-2026-22793","record":{"aliases":["GHSA-wg3x-7c26-97wj"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"AI desktop assistant","requires_auth":"none","summary":"Attackers can execute arbitrary JavaScript and achieve remote code execution by submitting malicious ECharts code blocks to the 5ire AI assistant.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"5ire","vendor":"5ire"}],"cvss":{"score":9.7,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"5ire vulnerable to Remote Code Execution (RCE) via ECharts","id":"CVE-2026-22793","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Account Takeover Vulnerability in Appsmith","id":"CVE-2026-22794"},"packages":[],"prev":{"headline":"5ire vulnerable to Remote Code Execution (RCE)","id":"CVE-2026-22792"},"products":["5ire"],"published":"2026-01-21","related":[{"cvss_score":9.7,"headline":"5ire vulnerable to Remote Code Execution (RCE)","id":"CVE-2026-22792","kev_date_added":null,"published":"2026-01-21"},{"cvss_score":9.7,"headline":"5ire vulnerable to Remote Code Execution (RCE) via mermaid","id":"CVE-2025-68669","kev_date_added":null,"published":"2025-12-23"},{"cvss_score":9.7,"headline":"5ire Chat Message XSS Vulnerability Enables Remote Code Execution","id":"CVE-2025-58357","kev_date_added":null,"published":"2025-09-04"},{"cvss_score":9.7,"headline":"5ire Client Vulnerable to Cross-Site Scripting (XSS) and Remote Code Execution (RCE)","id":"CVE-2025-47777","kev_date_added":null,"published":"2025-05-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-01-21","vendors":["nanbingxyz"]},"summary":"Attackers can execute arbitrary JavaScript and achieve remote code execution by submitting malicious ECharts code blocks to the 5ire AI assistant.","url":"https://insights.sbomify.com/CVE-2026-22793/"}