# CVE-2026-130839: ModelScope 1.11.0 to before 1.40.1 Unsafe Reflection RCE via syncdreamer.yaml


- **Severity:** High 8.5 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-gp8m-xpr4-qj9w

## What is CVE-2026-130839?

CVE-2026-130839 is a high-severity vulnerability in ModelScope, published on 17 Nov 2026. 

### Official description

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.

Weakness: CWE-470 (Use of Externally-Controlled Input to Select Classes or Code)

## Which versions are affected by CVE-2026-130839?

1 open source package ship an affected version, including modelscope.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `modelscope` | PyPI | `pkg:pypi/modelscope` | From 1.11.0 | 1.40.1 |

## How do I fix CVE-2026-130839?

Upgrade modelscope to 1.40.1 or later.

## Is CVE-2026-130839 being exploited?

There is no known exploitation of CVE-2026-130839 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130839 and fix it if it is affected.

What it is: CVE-2026-130839 is a high-severity vulnerability in ModelScope, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130839 in the wild and no public exploit code.

Affected packages and fixed versions:
- modelscope (PyPI): affected from 1.11.0; fixed in 1.40.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130839/ (Markdown: https://insights.sbomify.com/CVE-2026-130839/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130839
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130839
- OSV: https://osv.dev/vulnerability/CVE-2026-130839

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130839/
Summaries are generated and may contain mistakes; the official description above is the record.
