CVE-2026-45184 json
Kdenlive before 26.04.1 allows dangerous proxy parameters when an attacker-controlled project file is used.
published 2026-05-09 6 mo ago modified 2026-07-20 3 mo ago also EUVD-2026-28946
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 4%
- public exploits
- 0
- none known
Summary
Kdenlive before 26.04.1 allows dangerous proxy parameters when an attacker-controlled project file is used.
Patch / fix
- KDE Kdenlive 26.04.1
- kdenlive Debian 12 22.12.3-2+deb12u2
- kdenlive Debian 13 24.12.3-2+deb13u1
- kdenlive Debian 14 26.04.1-1
debian advisories DEBIAN-CVE-2026-45184
- kdenlive Ubuntu 26.04 LTS 4:25.12.3-0ubuntu1.1
ubuntu advisories UBUNTU-CVE-2026-45184
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-45184 updated cvss 7.3
Kdenlive: Kdenlive: Arbitrary code execution via malicious project file
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 5 mo ago
Exploit prediction
0.15% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L |
Affected products
- KDE Kdenlive
Classification
- Weakness
-
- CWE-829 Inclusion of Functionality from Untrusted Control Sphere
References
Sources
- CVE List CVE-2026-45184
- NVD CVE-2026-45184
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.