{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-32898 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"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."},"fix_prompt":"Check this codebase for CVE-2025-32898 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2025-32898 in the wild and no public exploit code.\n\nAffected product: KDE Connect verification-code protocol. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-32898/ (Markdown: https://insights.sbomify.com/CVE-2025-32898/index.md)","id":"CVE-2025-32898","markdown":"https://insights.sbomify.com/CVE-2025-32898/index.md","name":"CVE-2025-32898","record":{"aliases":["DEBIAN-CVE-2025-32898","GHSA-r3v4-hrwm-cxm5","UBUNTU-CVE-2025-32898"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"KDE Connect","requires_auth":"none","summary":"Weak verification codes in KDE Connect allow brute-force attacks, potentially leading to unauthorized device pairing and account takeover.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":4.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-331","name":"Insufficient Entropy"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Weak cryptography in KDE Connect verification-code protocol","id":"CVE-2025-32898","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in KDEConnect","id":"CVE-2025-32899"},"packages":[],"prev":{"headline":"Apache Seata (incubating): Deserialization of untrusted Data in Apache Seata Server","id":"CVE-2025-32897"},"products":["KDE Connect verification-code protocol"],"published":"2025-12-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-05","vendors":["KDE"]},"summary":"Weak verification codes in KDE Connect allow brute-force attacks, potentially leading to unauthorized device pairing and account takeover.","url":"https://insights.sbomify.com/CVE-2025-32898/"}