# CVE-2025-32898: Weak cryptography in KDE Connect verification-code protocol

> Weak verification codes in KDE Connect allow brute-force attacks, potentially leading to unauthorized device pairing and account takeover.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Dec 2025
- **Updated:** 5 Dec 2025
- **Also known as:** DEBIAN-CVE-2025-32898, GHSA-r3v4-hrwm-cxm5, UBUNTU-CVE-2025-32898

## What is CVE-2025-32898?

CVE-2025-32898 is a medium-severity vulnerability in KDE Connect verification-code protocol, published on 5 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The KDE Connect verification-code protocol before 2025-04-18 uses only 8 characters and therefore allows brute-force attacks. 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.

Weakness: CWE-331 (Insufficient Entropy)

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


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

Upgrade to a fixed version.

## Is CVE-2025-32898 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-32898 is a medium-severity vulnerability in KDE Connect verification-code protocol, published on 5 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-32898 in the wild and no public exploit code.

Affected product: KDE Connect verification-code protocol. 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-32898/ (Markdown: https://insights.sbomify.com/CVE-2025-32898/index.md)
```

## Sources

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

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