{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27917 exists.","fix":"No fix has been published for CVE-2025-27917 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-27917 is a high-severity vulnerability in n/a, published on 6 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-27917 and fix it if it is affected.\n\nWhat it is: CVE-2025-27917 is a high-severity vulnerability in n/a, published on 6 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27917 exists.\n\nAffected product: n/a. 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-27917/ (Markdown: https://insights.sbomify.com/CVE-2025-27917/index.md)","id":"CVE-2025-27917","markdown":"https://insights.sbomify.com/CVE-2025-27917/index.md","name":"CVE-2025-27917","record":{"aliases":["GHSA-3ghq-53cj-qqmp"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Remote desktop software","requires_auth":"none","summary":"Remote attackers can cause a denial of service in AnyDesk clients via incorrect deserialization leading to a null pointer dereference.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"anydesk","vendor":"anydesk"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"An issue was discovered in AnyDesk for Windows before 9.0.5, AnyDesk for macOS before 9.0.1, AnyDesk for Linux before 7.0.0, AnyDesk for iOS before 7.1.2, and AnyDesk for Android before 8.0.0. Remote Denial of Service can occur because of incorrect deserialization that results in failed memory allocation and a NULL pointer dereference.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Null dereference in n/a","id":"CVE-2025-27917","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Integer overflow in n/a","id":"CVE-2025-27918"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2025-27916"},"products":["n/a"],"published":"2025-11-06","related":[{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2025-27918","kev_date_added":null,"published":"2025-11-06"},{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2020-13160","kev_date_added":null,"published":"2020-06-09"},{"cvss_score":9.8,"headline":"AnyDesk before 3.6.1 on Windows has a DLL injection vulnerability.","id":"CVE-2017-14397","kev_date_added":null,"published":"2017-09-12"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2021-44426","kev_date_added":null,"published":"2022-09-12"},{"cvss_score":8.5,"headline":"AnyDesk 2.5.0 Unquoted Service Path Elevation of Privilege","id":"CVE-2016-20094","kev_date_added":null,"published":"2026-06-19"},{"cvss_score":8.5,"headline":"AnyDesk 5.4.0 - Unquoted Service Path","id":"CVE-2019-25261","kev_date_added":null,"published":"2026-02-03"},{"cvss_score":8.2,"headline":"Missing authorization in n/a","id":"CVE-2025-27919","kev_date_added":null,"published":"2025-11-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-08","vendors":["n/a"]},"summary":"Remote attackers can cause a denial of service in AnyDesk clients via incorrect deserialization leading to a null pointer dereference.","url":"https://insights.sbomify.com/CVE-2025-27917/"}