Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-52663: Vulnerability in Ubiquiti Inc UniFi Talk Touch

0
High
VulnerabilityCVE-2025-52663cvecve-2025-52663
Published: Thu Oct 30 2025 (10/30/2025, 23:30:28 UTC)
Source: CVE Database V5
Vendor/Project: Ubiquiti Inc
Product: UniFi Talk Touch

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.

AI-Powered Analysis

AILast updated: 12/02/2025, 19:29:26 UTC

Technical Analysis

CVE-2025-52663 is a vulnerability discovered in Ubiquiti Inc's UniFi Talk product line, specifically affecting UniFi Talk Touch (≤1.21.16), Talk Touch Max (≤2.21.22), and Talk G3 Phones (≤3.21.26). The root cause is the unintended retention of internal debugging functionality enabled on these devices. This debugging interface is accessible through the device API and can be invoked by an attacker who has access to the UniFi Talk management network segment. Because the vulnerability does not require authentication (PR:N) or user interaction (UI:N), and has a network attack vector (AV:N), it presents a significant risk. The vulnerability is classified under CWE-489 (Leftover Debug Code), which often leads to information disclosure or unauthorized control. Successful exploitation could allow an attacker to perform unauthorized debug operations, potentially leading to leakage of sensitive information, manipulation of device behavior, or denial of service. The CVSS v3.1 base score is 7.3 (high), reflecting the ease of exploitation and the impact on confidentiality, integrity, and availability. Although no known exploits have been reported in the wild, the presence of such debug functionality in production devices is a serious security oversight. Mitigation involves updating affected devices to versions 1.21.17 or later for Talk Touch, 2.21.23 or later for Talk Touch Max, and 3.21.27 or later for Talk G3 Phones, which disable the debug functionality.

Potential Impact

For European organizations, this vulnerability poses a significant threat to the security and reliability of their telephony infrastructure. UniFi Talk devices are often deployed in enterprise environments for VoIP communications, making them critical for daily operations. Exploitation could lead to unauthorized access to call data, interception or manipulation of communications, and disruption of telephony services, impacting business continuity and confidentiality. Given the network-based attack vector and lack of authentication requirement, attackers who gain access to the management network—whether through lateral movement or misconfigurations—could leverage this vulnerability to escalate their foothold. This risk is amplified in sectors with stringent privacy and data protection requirements, such as finance, healthcare, and government agencies. Additionally, disruption of telephony services could affect emergency communications and operational coordination. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as threat actors may develop exploits once the vulnerability is public. Therefore, timely patching is critical to mitigate potential impacts.

Mitigation Recommendations

1. Immediate deployment of firmware updates to the fixed versions: 1.21.17+ for UniFi Talk Touch, 2.21.23+ for Talk Touch Max, and 3.21.27+ for Talk G3 Phones. 2. Restrict network access to the UniFi Talk management network segment using network segmentation and firewall rules to limit exposure only to trusted administrators. 3. Implement strict access controls and monitoring on management interfaces to detect anomalous API calls or debug operation attempts. 4. Conduct regular audits of device configurations to ensure no leftover debug or test functionalities are enabled. 5. Employ network intrusion detection systems (NIDS) tuned to detect unusual API usage patterns associated with debug operations. 6. Educate IT staff about the vulnerability and the importance of applying patches promptly. 7. For environments where immediate patching is not feasible, consider isolating affected devices from untrusted networks or deploying compensating controls such as VPNs with strong authentication for management access.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
hackerone
Date Reserved
2025-06-18T15:00:00.895Z
Cvss Version
null
State
PUBLISHED

Threat ID: 6903f7a3aebfcd5474a44750

Added to database: 10/30/2025, 11:41:23 PM

Last enriched: 12/2/2025, 7:29:26 PM

Last updated: 12/15/2025, 9:52:31 AM

Views: 535

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats