{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-64621 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2026-64621 is a critical use after free vulnerability in Freerdp Freerdp, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-64621 and fix it if it is affected.\n\nWhat it is: CVE-2026-64621 is a critical use after free vulnerability in Freerdp Freerdp, published on 20 Jul 2026. 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-2026-64621 exists.\n\nAffected product: Freerdp Freerdp. 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-2026-64621/ (Markdown: https://insights.sbomify.com/CVE-2026-64621/index.md)","id":"CVE-2026-64621","markdown":"https://insights.sbomify.com/CVE-2026-64621/index.md","name":"CVE-2026-64621","record":{"aliases":["DEBIAN-CVE-2026-64621","GHSA-7pv2-4c55-cg52","GHSA-f27x-frr8-j9hc","UBUNTU-CVE-2026-64621"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"FreeRDP client","requires_auth":"none","summary":"An attacker can trigger a double-free vulnerability in FreeRDP clients by tricking a user into opening a malicious .rdp file, potentially leading to code execution or crashes.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"freerdp","vendor":"freerdp"}],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-415","name":"Double Free"}],"description":"FreeRDP before 3.28.0 (affected 3.x through 3.27.1) contains a double-free vulnerability in freerdp_client_rdp_file_apply_to_settings() (client/common/file.c) when parsing the selectedmonitors field of a .rdp connection file. The MonitorIds array is allocated through the settings object, and a raw non-owning pointer to it is freed on the strtoul error path without clearing settings-\u003eMonitorIds, leaving it dangling; at teardown freerdp_settings_free() frees the same buffer again. An attacker who convinces a victim to open a crafted .rdp file with oversized monitor tokens can trigger a size-controlled double-free in any FreeRDP CLI client (xfreerdp/sdl-freerdp/wlfreerdp) in the default configuration.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"FreeRDP before 3.28.0 Double-Free via selectedmonitors","id":"CVE-2026-64621","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"freerdp:freerdp","products":["freerdp:freerdp"],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Network-AI 5.12.2 through 5.13.3 Missing Authorization via ApprovalInbox","id":"CVE-2026-64622"},"packages":[],"prev":{"headline":"FreeRDP before 3.28.0 Heap Buffer Overflow via crypto_rsa_common","id":"CVE-2026-64620"},"products":["FreeRDP"],"published":"2026-07-20","related":[{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2021-37594","kev_date_added":null,"published":"2021-07-27"},{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2021-37595","kev_date_added":null,"published":"2021-07-27"},{"cvss_score":9.4,"headline":"FreeRDP Windows Client before 3.29.0 Heap Buffer Overflow via Cliprdr","id":"CVE-2026-67305","kev_date_added":null,"published":"2026-08-01"},{"cvss_score":9.3,"headline":"FreeRDP before 3.29.0 TLS Certificate Identity Validation Bypass","id":"CVE-2026-66402","kev_date_added":null,"published":"2026-08-01"},{"cvss_score":9.3,"headline":"FreeRDP before 3.29.0 HTTP Proxy Request Injection via Redirection","id":"CVE-2026-67289","kev_date_added":null,"published":"2026-08-01"},{"cvss_score":9.3,"headline":"FreeRDP before 3.29.0 WebSocket Ping Buffer Over-disclosure","id":"CVE-2026-67292","kev_date_added":null,"published":"2026-08-01"},{"cvss_score":9.3,"headline":"FreeRDP before 3.29.0 Improper Certificate Hostname Validation","id":"CVE-2026-67293","kev_date_added":null,"published":"2026-08-01"}],"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-23","vendors":["FreeRDP"]},"summary":"An attacker can trigger a double-free vulnerability in FreeRDP clients by tricking a user into opening a malicious .rdp file, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/CVE-2026-64621/"}