Skip to main content
VulnerabilityPublished

CVE-2026-2256: ModelScope ms-agent · Code Injection

Affects ModelScope ms-agentSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.7% chance of exploitation in 30 days – higher than 77% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  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), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
ModelScopems-agentAffected
  • =0
Fixed in–

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

AI-suggested

To mitigate CVE-2026-2256, organizations should prioritize the following actions: 1) Monitor ModelScope’s official channels for patches or updates addressing this vulnerability and apply them promptly once available. 2) Implement strict input validation and sanitization on all data fed into ms-agent, especially prompt-derived inputs, to prevent injection of malicious commands. 3) Employ sandboxing or containerization techniques to isolate the ms-agent process, limiting the potential impact of command execution. 4) Restrict network access to ms-agent instances to trusted sources only, using firewalls and network segmentation. 5) Enable comprehensive logging and monitoring to detect anomalous command executions or suspicious activity related to ms-agent. 6) Conduct regular security assessments and code reviews focusing on input handling in AI agents and automation tools. 7) Educate development and operations teams about secure coding practices to avoid similar code injection vulnerabilities in future AI components.

Description

A command injection vulnerability in ModelScope's ms-agent versions v1.6.0rc1 and earlier exists, allowing an attacker to execute arbitrary operating system commands through crafted prompt-derived input.

References

Community reviews

Loading reviews…