# CVE-2025-23115: Use after free in UniFi Protect Cameras

> A use-after-free flaw in UniFi Protect Cameras allows remote code execution for attackers on the management network.

- **Severity:** Critical 9.0 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Mar 2025
- **Updated:** 13 Mar 2025
- **Also known as:** GHSA-9gc7-wxx3-hpww

## What is CVE-2025-23115?

CVE-2025-23115 is a critical use after free vulnerability in Ubiquiti Inc UniFi Protect Cameras, published on 1 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Use After Free vulnerability on UniFi Protect Cameras could allow a Remote Code Execution (RCE) by a malicious actor with access to UniFi Protect Cameras management network.

Weakness: CWE-416 (Use After Free)

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


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

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

## Is CVE-2025-23115 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-23115 is a critical use after free vulnerability in Ubiquiti Inc UniFi Protect Cameras, published on 1 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-23115 in the wild and no public exploit code.

Affected product: Ubiquiti Inc UniFi Protect Cameras. 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-23115/ (Markdown: https://insights.sbomify.com/CVE-2025-23115/index.md)
```

## Sources

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

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