CVE-2025-66270: CWE-290 Authentication Bypass by Spoofing in KDE KDE Connect protocol
The KDE Connect protocol 8 before 2025-11-28 does not correlate device IDs across two packets. This affects KDE Connect before 25.12 on desktop, KDE Connect before 0.5.4 on iOS, KDE Connect before 1.34.4 on Android, GSConnect before 68, and Valent before 1.0.0.alpha.49.
AI Analysis
Technical Summary
CVE-2025-66270 is a medium-severity authentication bypass vulnerability identified in the KDE Connect protocol, which facilitates seamless integration and communication between desktop and mobile devices. The root cause is the protocol's failure to correlate device IDs consistently across two separate packets during the authentication process. This flaw allows an attacker with network access to spoof device identities, effectively bypassing authentication controls. The affected versions include KDE Connect before 25.12 on desktop, versions before 0.5.4 on iOS, before 1.34.4 on Android, GSConnect before 68, and Valent before 1.0.0.alpha.49. The vulnerability is classified under CWE-290 (Authentication Bypass by Spoofing). The CVSS v3.1 base score is 4.7, reflecting an attack vector requiring adjacent network access (AV:A), high attack complexity (AC:H), no privileges required (PR:N), and no user interaction (UI:N). The scope is changed (S:C), indicating that the vulnerability affects resources beyond the initially vulnerable component. The impact on confidentiality and integrity is low, with no impact on availability. No public exploits have been reported yet, but the vulnerability's presence in widely used KDE Connect implementations across multiple platforms makes it a relevant concern. The KDE project has not yet published official patches at the time of this report, so users should monitor for updates and apply them promptly once available.
Potential Impact
For European organizations, the impact of CVE-2025-66270 primarily concerns the confidentiality and integrity of data exchanged between devices using KDE Connect and related software. Since KDE Connect is popular among Linux desktop users and integrates with Android and iOS devices, organizations with employees using these tools for device synchronization, file transfer, or remote control could face unauthorized access risks. Attackers exploiting this vulnerability could impersonate trusted devices, potentially intercepting or manipulating data streams, leading to data leakage or unauthorized command execution on connected devices. Although the vulnerability does not affect availability, the breach of confidentiality and integrity could compromise sensitive corporate information or user privacy. Industries with high reliance on secure device communication, such as finance, government, and technology sectors, may be particularly vulnerable. The medium severity and high attack complexity reduce the likelihood of widespread exploitation, but targeted attacks remain a concern, especially in environments where network segmentation is weak or where KDE Connect is used extensively.
Mitigation Recommendations
To mitigate CVE-2025-66270, European organizations should: 1) Immediately inventory all devices running KDE Connect, GSConnect, or Valent to identify affected versions. 2) Monitor KDE project announcements and apply official patches or updates as soon as they are released, upgrading to KDE Connect 25.12 or later, iOS version 0.5.4 or later, Android version 1.34.4 or later, GSConnect 68 or later, and Valent 1.0.0.alpha.49 or later. 3) Implement network segmentation and restrict access to local networks where KDE Connect is used to limit potential attacker proximity. 4) Disable KDE Connect or related services on devices where it is not essential to reduce the attack surface. 5) Employ network monitoring tools to detect anomalous device communication patterns that could indicate spoofing attempts. 6) Educate users about the risks of connecting to untrusted networks or devices and encourage the use of VPNs or secure channels when using KDE Connect. 7) Consider alternative secure device synchronization tools if timely patching is not feasible. These steps go beyond generic advice by focusing on proactive inventory, network controls, and user awareness tailored to the KDE Connect ecosystem.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Poland, Italy, Spain
CVE-2025-66270: CWE-290 Authentication Bypass by Spoofing in KDE KDE Connect protocol
Description
The KDE Connect protocol 8 before 2025-11-28 does not correlate device IDs across two packets. This affects KDE Connect before 25.12 on desktop, KDE Connect before 0.5.4 on iOS, KDE Connect before 1.34.4 on Android, GSConnect before 68, and Valent before 1.0.0.alpha.49.
AI-Powered Analysis
Technical Analysis
CVE-2025-66270 is a medium-severity authentication bypass vulnerability identified in the KDE Connect protocol, which facilitates seamless integration and communication between desktop and mobile devices. The root cause is the protocol's failure to correlate device IDs consistently across two separate packets during the authentication process. This flaw allows an attacker with network access to spoof device identities, effectively bypassing authentication controls. The affected versions include KDE Connect before 25.12 on desktop, versions before 0.5.4 on iOS, before 1.34.4 on Android, GSConnect before 68, and Valent before 1.0.0.alpha.49. The vulnerability is classified under CWE-290 (Authentication Bypass by Spoofing). The CVSS v3.1 base score is 4.7, reflecting an attack vector requiring adjacent network access (AV:A), high attack complexity (AC:H), no privileges required (PR:N), and no user interaction (UI:N). The scope is changed (S:C), indicating that the vulnerability affects resources beyond the initially vulnerable component. The impact on confidentiality and integrity is low, with no impact on availability. No public exploits have been reported yet, but the vulnerability's presence in widely used KDE Connect implementations across multiple platforms makes it a relevant concern. The KDE project has not yet published official patches at the time of this report, so users should monitor for updates and apply them promptly once available.
Potential Impact
For European organizations, the impact of CVE-2025-66270 primarily concerns the confidentiality and integrity of data exchanged between devices using KDE Connect and related software. Since KDE Connect is popular among Linux desktop users and integrates with Android and iOS devices, organizations with employees using these tools for device synchronization, file transfer, or remote control could face unauthorized access risks. Attackers exploiting this vulnerability could impersonate trusted devices, potentially intercepting or manipulating data streams, leading to data leakage or unauthorized command execution on connected devices. Although the vulnerability does not affect availability, the breach of confidentiality and integrity could compromise sensitive corporate information or user privacy. Industries with high reliance on secure device communication, such as finance, government, and technology sectors, may be particularly vulnerable. The medium severity and high attack complexity reduce the likelihood of widespread exploitation, but targeted attacks remain a concern, especially in environments where network segmentation is weak or where KDE Connect is used extensively.
Mitigation Recommendations
To mitigate CVE-2025-66270, European organizations should: 1) Immediately inventory all devices running KDE Connect, GSConnect, or Valent to identify affected versions. 2) Monitor KDE project announcements and apply official patches or updates as soon as they are released, upgrading to KDE Connect 25.12 or later, iOS version 0.5.4 or later, Android version 1.34.4 or later, GSConnect 68 or later, and Valent 1.0.0.alpha.49 or later. 3) Implement network segmentation and restrict access to local networks where KDE Connect is used to limit potential attacker proximity. 4) Disable KDE Connect or related services on devices where it is not essential to reduce the attack surface. 5) Employ network monitoring tools to detect anomalous device communication patterns that could indicate spoofing attempts. 6) Educate users about the risks of connecting to untrusted networks or devices and encourage the use of VPNs or secure channels when using KDE Connect. 7) Consider alternative secure device synchronization tools if timely patching is not feasible. These steps go beyond generic advice by focusing on proactive inventory, network controls, and user awareness tailored to the KDE Connect ecosystem.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- mitre
- Date Reserved
- 2025-11-26T00:00:00.000Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69327175f88dbe026c7799fa
Added to database: 12/5/2025, 5:45:25 AM
Last enriched: 12/12/2025, 6:02:52 AM
Last updated: 1/19/2026, 8:41:58 PM
Views: 82
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-23852: CWE-94: Improper Control of Generation of Code ('Code Injection') in siyuan-note siyuan
MediumCVE-2026-1174: Resource Consumption in birkir prime
MediumCVE-2026-23837: CWE-863: Incorrect Authorization in franklioxygen MyTube
CriticalCVE-2026-23851: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in siyuan-note siyuan
HighCVE-2026-23850: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in siyuan-note siyuan
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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.