Skip to main content
CVE-2025-67744VulnerabilityPublished

CVE-2025-67744: ThinkInAIXYZ deepchat · Code Injection

Affects ThinkInAIXYZ deepchatSource CVE Database V5

0

Not known to be exploited · CVSS 9.7 Critical : upgrade to 0.5.3 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.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.5.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 16 Dec 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

Upgrade thinkinaixyz/deepchat to 0.5.3.

Affected software

ProductAffectedFixed in
GitHubthinkinaixyz/deepchatpkg:github/thinkinaixyz/deepchatOther threatsAffected
  • <0.5.3
Fixed in
  • 0.5.3

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

AI-suggested

1. Immediate upgrade of all DeepChat instances to version 0.5.3 or later, which contains the patch addressing the unsafe Mermaid configuration and IPC exposure. 2. Audit and restrict Electron IPC interfaces to ensure they are not exposed unnecessarily to the DOM or untrusted inputs. 3. Implement strict input validation and sanitization on Mermaid diagram data to prevent injection of malicious JavaScript code. 4. Employ network segmentation and firewall rules to limit access to DeepChat services, especially from untrusted networks. 5. Monitor logs and network traffic for unusual activity indicative of exploitation attempts, such as unexpected command executions or IPC calls. 6. Conduct security reviews of any custom integrations or plugins that interact with Mermaid or Electron IPC to ensure they do not introduce similar vulnerabilities. 7. Educate users about the risks of opening untrusted Mermaid diagrams or AI agent inputs that could trigger code execution. 8. Consider deploying runtime application self-protection (RASP) or endpoint detection and response (EDR) solutions to detect and block exploitation attempts in real time. 9. Maintain an incident response plan tailored to AI platform compromises, including containment and recovery procedures. These steps go beyond generic patching by addressing the root causes and operational security controls necessary to mitigate this complex vulnerability.

Description

DeepChat is an open-source artificial intelligence agent platform that unifies models, tools, and agents. Prior to version 0.5.3, a security vulnerability exists in the Mermaid diagram rendering component that allows arbitrary JavaScript execution. Due to the exposure of the Electron IPC renderer to the DOM, this Cross-Site Scripting (XSS) flaw escalates to full Remote Code Execution (RCE), allowing an attacker to execute arbitrary system commands. Two concurrent issues, unsafe Mermaid configuration and an exposed IPC interface, cause this issue. Version 0.5.3 contains a patch.

References

Community reviews

Loading reviews…