jxxghp MoviePilot Workflow Fork Endpoint workflow.py WorkflowExecutor.restore_context deserialization
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected product is MoviePilot up to 3.1.2 (advisory states affected versions <= v3.1.1 for the CVE writeup) Workflow must have a persisted legacy Base64-pickle context (context.content) that is read by restore_context during execution Workflow must be run with from_begin=false or triggered via the event path, since the default from_begin=true resets the context
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 13/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fix or patch referenced
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
MoviePilot, an open-source media management application, is affected through its workflow fork feature, where a remotely triggered flaw in how workflow context is restored can lead to unsafe deserialization of data. Successful exploitation could allow an attacker to run unintended code or manipulate the application's behavior on the affected server.
Read the original 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.
What to do
Check whether your setup matches what the bug needs.
Affected product is MoviePilot up to 3.1.2 (advisory states affected versions <= v3.1.1 for the CVE writeup) Workflow must have a persisted legacy Base64-pickle context (context.content) that is read by restore_context during execution Workflow must be run with from_begin=false or triggered via the event path, since the default from_begin=true resets the contextApply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- jxxghp MoviePilot
3.1.0, 3.1.1, 3.1.2
Evidence 9
- Advisory
- Advisory
- Advisory
- Advisory
- Patch
Show all 9 sourcesShow fewer sources
- Patch
- Patch
- Exploit
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120320
What does this mean?
The workflow restore code decodes a stored legacy context with Base64 and passes it to pickle.loads(). A crafted stored value can therefore run arbitrary OS commands with MoviePilot service privileges when the workflow is restored and run.Source: github.com
Am I affected, and how do I check?
The advisory lists MoviePilot up to 3.1.2, while the CVE writeup says v3.1.1 and earlier, so compare your installed version against both. The issue needs a workflow with a persisted legacy Base64-pickle context that runs with from_begin=false or through the event-triggered path, and the attacker must hold manage permission.Source: github.com
What should I do about it?
The checked facts do not name a fixed version or a workaround. Check the jxxghp MoviePilot project advisory for an upgrade target before relying on any version.Source: github.com
Is it 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