Quick answers
- Is CVE-2026-45184 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45184 being exploited in the wild.
- How severe is CVE-2026-45184?
- Medium severity, with a CVSS score of 6.5, published 9 May 2026.
- Which products and versions are affected?
- Kdenlive < 26.04.1.
- Is there a fix for CVE-2026-45184?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-45184 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-45184?
- Check whether you run Kdenlive at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A vulnerability exists in Kdenlive's handling of proxy parameters within project files (CWE-829). The application failed to properly sanitize parameters passed to the underlying FFmpeg process during proxy clip generation. An attacker can craft a malicious project file containing dangerous FFmpeg arguments (such as -attach, -metadata, or protocol_whitelist) to achieve arbitrary code execution or file exfiltration. Exploitation requires a user to open a specially crafted .kdenlive project file. The issue is resolved in version 26.04.1 by implementing a blocklist for sensitive parameters and enforcing a strict protocol whitelist (file, pipe).
Affected products
- KDE Kdenlive < 26.04.1
Timeline
- 2026-04-03: other: Initial proxy parameter cleanup commit authored
- 2026-04-24: other: Parameter sanitization commit authored
- 2026-05-08: advisory: KDE Project Security Advisory released
- 2026-05-09: disclosed: CVE published to NVD