Skip to main content
CVE-2025-59053VulnerabilityPublished

CVE-2025-59053: moeru-ai airi · Code Injection

Affects moeru-ai airiSource CVE Database V5

0

Not known to be exploited · CVSS 9.7 Critical · fixed in 0.7.2 : patch moeru-ai airi as a priority.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.7Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.7.2
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 11 Sep 2025

  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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
moeru-ai airiAffected
  • =0.7.2-beta.2
Fixed in–

AI-suggested

1. Immediate upgrade to AIRI version 0.7.2-beta.3 or later, where the vulnerability is fixed. 2. Implement strict input validation and sanitization on all Markdown content before rendering, using well-maintained libraries that escape or remove dangerous HTML/JavaScript. 3. Restrict or disable the Tauri API command execution interface unless absolutely necessary; if required, enforce strict whitelisting of allowed commands and arguments. 4. Employ Content Security Policy (CSP) headers to limit the impact of potential XSS by restricting script sources and execution contexts. 5. Conduct thorough code audits and penetration testing focusing on frontend-backend interaction surfaces, especially where user input is passed to system commands. 6. Monitor logs for unusual command execution patterns or unexpected API calls. 7. Educate developers and administrators on secure coding practices and the risks of direct DOM injection without sanitization. 8. For organizations unable to upgrade immediately, consider isolating AIRI deployments in segmented network zones with limited privileges to reduce potential impact.

Description

AIRI is a self-hosted, artificial intelligence based Grok Companion. In v0.7.2-beta.2 in the `packages/stage-ui/src/components/MarkdownRenderer.vue` path, the Markdown content is processed using the useMarkdown composable, and the processed HTML is rendered directly into the DOM using v-html. An attacker creates a card file containing malicious HTML/JavaScript, then simply processes it using the highlightTagToHtml function (which simply replaces template tags without HTML escaping), and then directly renders it using v-html, leading to cross-site scripting (XSS). The project also exposes the Tauri API, which can be called from the frontend. The MCP plugin exposes a command execution interface function in `crates/tauri-plugin-mcp/src/lib.rs`. This allows arbitrary command execution. `connect_server` directly passes the user-supplied `command` and `args` parameters to `Command::new(command).args(args)` without any input validation or whitelisting. Thus, the previous XSS exploit could achieve command execution through this interface.v0.7.2-beta.3 fixes the issue.

References

Community reviews

Loading reviews…