# CVE-2025-52663: Security feature bypass in UniFi Talk G3 Phones

> Attackers on the management network can invoke internal debug operations due to unintentionally enabled debugging features in UniFi Talk devices.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Oct 2025
- **Updated:** 2 Dec 2025
- **Also known as:** GHSA-v532-7c4x-249v

## What is CVE-2025-52663?

CVE-2025-52663 is a high-severity vulnerability in Ubiquiti Inc UniFi Talk G3 Phones, published on 30 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was identified in certain UniFi Talk devices where internal debugging functionality remained unintentionally enabled. This issue could allow an attacker with access to the UniFi Talk management network to invoke internal debug operations through the device API.


Affected Products:
UniFi Talk Touch (Version 1.21.16 and earlier) 
UniFi Talk Touch Max (Version 2.21.22 and earlier) 
UniFi Talk G3 Phones (Version 3.21.26 and earlier) 
 
Mitigation:
Update the UniFi Talk Touch to Version 1.21.17 or later.
Update the UniFi Talk Touch Max to Version 2.21.23 or later.
Update the UniFi Talk G3 Phones to Version 3.21.27 or later.

Weakness: CWE-489 (Active Debug Code)

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


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

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

## Is CVE-2025-52663 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52663 is a high-severity vulnerability in Ubiquiti Inc UniFi Talk G3 Phones, published on 30 Oct 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-52663 in the wild and no public exploit code.

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

## Sources

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

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