{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67294 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2026-67294 is a critical vulnerability in Freerdp Freerdp, published on 1 Aug 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-67294 and fix it if it is affected.\n\nWhat it is: CVE-2026-67294 is a critical vulnerability in Freerdp Freerdp, published on 1 Aug 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-67294 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-67294/ (Markdown: https://insights.sbomify.com/CVE-2026-67294/index.md)","id":"CVE-2026-67294","markdown":"https://insights.sbomify.com/CVE-2026-67294/index.md","name":"CVE-2026-67294","record":{"aliases":["DEBIAN-CVE-2026-67294","GHSA-89c6-jjrw-96h4","GHSA-v6mf-3jqv-cgr7","UBUNTU-CVE-2026-67294"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"FreeRDP client library","requires_auth":"none","summary":"FreeRDP clients may accept invalid server certificates due to flawed EKU validation, allowing man-in-the-middle attacks in environments relying on certificate purpose separation.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"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-295","name":"Improper Certificate Validation"}],"description":"FreeRDP before 3.29.0 improperly validates the Extended Key Usage (EKU) purpose of the peer certificate during client-side server TLS authentication. In x509_utils_verify(), when server-purpose (X509_PURPOSE_SSL_SERVER) verification fails, the code falls back to client-purpose and any-purpose verification, so a trusted, hostname-matching certificate valid only for clientAuth can be accepted as the RDP server certificate. In environments relying on EKU separation between client and server certificates, this allows a clientAuth-only certificate issued by a trusted CA to bypass server certificate purpose validation.","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.29.0 TLS Certificate EKU Bypass","id":"CVE-2026-67294","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"freerdp:freerdp","products":["freerdp:freerdp"],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"FreeRDP before 3.29.0 Path Traversal via drive redirection","id":"CVE-2026-67295"},"packages":[],"prev":{"headline":"FreeRDP before 3.29.0 Improper Certificate Hostname Validation","id":"CVE-2026-67293"},"products":["FreeRDP"],"published":"2026-08-01","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-08-03","vendors":["FreeRDP"]},"summary":"FreeRDP clients may accept invalid server certificates due to flawed EKU validation, allowing man-in-the-middle attacks in environments relying on certificate purpose separation.","url":"https://insights.sbomify.com/CVE-2026-67294/"}