# CVE-2026-120320: jxxghp MoviePilot Workflow Fork Endpoint workflow.py WorkflowExecutor.restore_context deserialization


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Nov 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-8gr5-327m-w3jx

## What is CVE-2026-120320?

CVE-2026-120320 is a medium-severity vulnerability in jxxghp MoviePilot, published on 2 Nov 2026. 

### Official description

A vulnerability was determined in jxxghp MoviePilot up to 3.1.2. This vulnerability affects the function WorkflowExecutor.restore_context of the file app/chain/workflow.py of the component Workflow Fork Endpoint. Executing a manipulation can lead to deserialization. The attack can be launched remotely. The exploit has been publicly disclosed and may be utilized. Upgrading to version 3.1.3 is able to resolve this issue. This patch is called 6034dcc880c13079aeb398dbe32c346ebcd3a6d2. It is recommended to upgrade the affected component.

Weakness: CWE-502 (Deserialization of Untrusted Data), CWE-20 (Improper Input Validation)

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


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

No fix has been published for CVE-2026-120320 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-120320 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120320 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120320 is a medium-severity vulnerability in jxxghp MoviePilot, published on 2 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120320 exists.

Affected product: jxxghp MoviePilot. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-120320/ (Markdown: https://insights.sbomify.com/CVE-2026-120320/index.md)
```

## Sources

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

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