dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-2256

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A command injection vulnerability exists in ModelScope's ms-agent versions v1.6.0rc1 and earlier, where crafted prompt-derived input is not properly sanitized before being passed to OS command execution, allowing arbitrary command execution.

MitigationImplement strict input validation and sanitization for all prompt-derived input before passing to system calls, preferably using parameterized commands or whitelist-based validation to prevent shell metacharacter injection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if ms-agent is installed
    Run 'pip show ms-agent' or 'pip list | grep ms-agent' to check for ModelScope agent package installation
    Affected if The package is present on the system
  2. Determine installed ms-agent version
    Check the version field from the pip show output or package metadata
    Affected if Version is v1.6.0rc1 or any earlier version (v1.6.0rc0, v1.5.x, etc.)
  3. Check if application accepts external prompt input
    Review application logs, configuration, or code that handles prompt-derived input to determine if user-controlled prompts can reach the agent processing pipeline
    Affected if The agent processes prompt input from untrusted sources without sanitization
  4. Identify command execution paths
    Inspect application configuration or runtime behavior to determine if OS command execution is invoked during prompt processing
    Affected if The agent invokes shell commands or system calls while processing prompts

You are affected if ms-agent v1.6.0rc1 or earlier is installed AND your environment allows prompt-derived input to reach the agent's command execution pathways.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and sanitization for all prompt-derived input before passing to system calls, preferably using parameterized commands or whitelist-based validation to prevent shell metacharacter injection.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation10.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,620
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2256 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2256 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data