# CVE-2026-45184: Code injection in Kdenlive

> An attacker can execute arbitrary code by tricking a user into opening a malicious project file in Kdenlive.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 9 May 2026
- **Updated:** 11 May 2026
- **Also known as:** DEBIAN-CVE-2026-45184, GHSA-8mfr-c96w-64p5, UBUNTU-CVE-2026-45184, USN-8856-1, openSUSE-SU-2026:20723-1

## What is CVE-2026-45184?

CVE-2026-45184 is a medium-severity code injection vulnerability in Kdenlive, published on 9 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Kdenlive before 26.04.1 allows dangerous proxy parameters when an attacker-controlled project file is used.

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

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


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

Upgrade to a fixed version.

## Is CVE-2026-45184 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45184 is a medium-severity code injection vulnerability in Kdenlive, published on 9 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-45184 in the wild and no public exploit code.

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

## Sources

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

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