Skip to main content
Menu
CVEs

CVE

ModelScope 1.11.0 to before 1.40.1 Unsafe Reflection RCE via syncdreamer.yaml

CVE-2026-130839EUVD-2026-127263GHSA-GP8M-XPR4-QJ9W

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

8.5HighCNA
Exploited
No known exploitation
Fix
Fixed in 1.40.1
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 1.40.1.

Published
Last modified
Reference
Last checked
26/100 · provisional
39% of modelscope downloads last week were affected versions (406.6K).PyPI, per-version counts from ClickPy, 1M downloads in the last 7 days, read Nov 14, 2026
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

ModelScope 1.11.0 to before 1.40.1 contains an unsafe reflection vulnerability in the image-to-3D SyncDreamer pipeline that allows remote attackers to execute code via crafted model configuration. Attackers can publish a model whose syncdreamer.yaml target field makes instantiate_from_config() import and instantiate any class with controlled params, without an allowlist or trust_remote_code check, executing code when victims load it.

cve.now Index

26Pcve.now Index 26 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure?/25Unknown. No advisory context yet
  • Reach16/20modelscope: 1.1M downloads a week
  • Severity9.5/10CVSS 8.5, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 81 if added to CISA KEV
  • Would score about 76 if CISA's SSVC rates exploitation active
  • Would score about 48 if advisories confirm default setups are exposed

Impact

  • Widely used

    modelscope has 1.1m weekly downloads.Source: pypistats.org

    411 packages depend on modelscope.Source: deps.dev

What to do

  • Upgrade to a fixed version: 1.40.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130839 (ModelScope 1.11.0 to before 1.40.1 Unsafe Reflection RCE via syncdreamer.yaml), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130839 (entry last updated 2026-11-17):
Affected:
- PyPI package modelscope: from 1.11.0, fixed in 1.40.1
Fixed versions: 1.40.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130839 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130839 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (PyPI): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/modelscope/modelscope/pull/1788
- https://github.com/modelscope/modelscope/commit/563133cfbc7af7891498d9928a1b018fa42ce30b
- https://github.com/modelscope/modelscope/releases/tag/v1.40.1
- https://github.com/modelscope/modelscope/blob/v1.40.0/modelscope/models/cv/image_to_3d/ldm/util.py
- https://github.com/modelscope/modelscope/blob/v1.40.0/modelscope/pipelines/cv/image_to_3d_pipeline.py
- https://www.vulncheck.com/advisories/modelscope-1.11.0-to-before-1.40.1-unsafe-reflection-rce-via-syncdreamer-yaml
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130839
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130839"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Affected versions

  • From 1.11.0 · fixed in 1.40.1

    Fixed in 1.40.1 (released Sep 15, 2026, 63 days before disclosure).

    The latest release, 1.40.3, is not affected.

Evidence 8

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 6

  1. Patch
  2. Patch
  3. Repository
  4. Repository
  5. Repository
  6. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130839

Is CVE-2026-130839 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-130839?

modelscope (PyPI): from 1.11.0 before 1.40.1.Source: cve.now feed data

How do I fix CVE-2026-130839?

Upgrade to a fixed version: 1.40.1.Source: cve.now feed data

More CVEs