# CVE-2025-1413: Dylib Hijacking in DaVinci Resolve

> Incorrect file permissions in DaVinci Resolve on macOS allow local attackers to hijack dynamic libraries, leading to privilege escalation and code execution.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Feb 2025
- **Updated:** 3 Oct 2025
- **Also known as:** GHSA-47m3-cr54-pvmq

## What is CVE-2025-1413?

CVE-2025-1413 is a high-severity vulnerability in Blackmagic Design Inc DaVinci Resolve, published on 28 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

DaVinci Resolve on MacOS was found to be installed with incorrect file permissions (rwxrwxrwx). This is inconsistent with standard macOS security practices, where applications should have drwxr-xr-x permissions. Incorrect permissions allow for Dylib Hijacking. Guest account, other users and applications can exploit this vulnerability for privilege escalation. This issue affects DaVinci Resolve on MacOS in versions before 19.1.3.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2025-1413?


## How do I fix CVE-2025-1413?

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

## Is CVE-2025-1413 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1413 and fix it if it is affected.

What it is: CVE-2025-1413 is a high-severity vulnerability in Blackmagic Design Inc DaVinci Resolve, published on 28 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-1413 in the wild and no public exploit code.

Affected product: Blackmagic Design Inc DaVinci Resolve. 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-2025-1413/ (Markdown: https://insights.sbomify.com/CVE-2025-1413/index.md)
```

## Sources

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

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