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-32900: CWE-348 Use of Less Trusted Source in KDE KDE Connect information-exchange protocol

0
Medium
VulnerabilityCVE-2025-32900cvecve-2025-32900cwe-348
Published: Fri Dec 05 2025 (12/05/2025, 00:00:00 UTC)
Source: CVE Database V5
Vendor/Project: KDE
Product: KDE Connect information-exchange protocol

Description

In the KDE Connect information-exchange protocol before 2025-04-18, a packet can be crafted to temporarily change the displayed information about a device, because broadcast UDP is used. This affects KDE Connect before 1.33.0 on Android, KDE Connect before 25.04 on desktop, KDE Connect before 0.5 on iOS, Valent before 1.0.0.alpha.47, and GSConnect before 59.

AI-Powered Analysis

AILast updated: 12/12/2025, 06:07:50 UTC

Technical Analysis

CVE-2025-32900 is a vulnerability classified under CWE-348 (Use of Less Trusted Source) affecting the KDE Connect information-exchange protocol. KDE Connect facilitates seamless communication and data exchange between devices such as Android phones, desktops, and iOS devices. The protocol relies on broadcast UDP packets to share device information across the local network. Due to the use of broadcast UDP, an attacker on the same network can craft malicious packets that temporarily modify the displayed information about a device, such as device name or status, misleading users or automated systems that rely on this data. This vulnerability affects multiple platforms including Android (KDE Connect <1.33.0), desktop (KDE Connect <25.04), iOS (KDE Connect <0.5), Valent (<1.0.0.alpha.47), and GSConnect (<59). The flaw does not compromise confidentiality or availability but impacts data integrity by allowing spoofed device information. The CVSS 3.1 base score is 4.3 (medium), reflecting that the attack vector is adjacent network (AV:A), with low attack complexity (AC:L), no privileges required (PR:N), and no user interaction (UI:N). No patches or exploits are currently documented, but the issue is publicly known since December 2025. The vulnerability highlights risks inherent in using broadcast UDP for device discovery and information exchange without strong authentication or validation mechanisms.

Potential Impact

For European organizations, the primary impact of CVE-2025-32900 is the potential for misinformation within local networks where KDE Connect or related products are deployed. This can lead to confusion or misidentification of devices, which may disrupt workflows relying on accurate device status or identity. While the vulnerability does not directly expose sensitive data or cause service disruption, it could be leveraged in targeted scenarios such as social engineering, network reconnaissance, or as part of a multi-stage attack chain. Organizations with high reliance on KDE Connect for device interoperability, especially in environments with many connected devices (e.g., enterprises, educational institutions, or public sector offices), may face increased risk. Since exploitation requires network proximity, the threat is more relevant in environments with shared or poorly segmented networks. The integrity compromise could also affect automated systems or scripts that depend on accurate device information, potentially leading to operational errors.

Mitigation Recommendations

To mitigate this vulnerability, European organizations should: 1) Update KDE Connect and related products (Valent, GSConnect) to the latest patched versions (Android ≥1.33.0, desktop ≥25.04, iOS ≥0.5, Valent ≥1.0.0.alpha.47, GSConnect ≥59) as soon as they become available. 2) Implement network segmentation and restrict broadcast traffic within local networks to limit exposure to untrusted devices. 3) Employ network monitoring to detect anomalous broadcast UDP packets that could indicate spoofing attempts. 4) Educate users about the risk of device information spoofing and encourage verification of device identities through alternative means when critical. 5) Consider disabling KDE Connect or related services on networks where device discovery is not essential or where security policies prohibit broadcast-based protocols. 6) Advocate for or contribute to enhancements in KDE Connect to incorporate stronger authentication or cryptographic validation of device information in future releases.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2025-04-14T00:00:00.000Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69327175f88dbe026c7799f6

Added to database: 12/5/2025, 5:45:25 AM

Last enriched: 12/12/2025, 6:07:50 AM

Last updated: 1/19/2026, 8:45:17 PM

Views: 91

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 more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats