{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-65908 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-65908 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-65908 is a high-severity code injection vulnerability in JetBrains PyCharm, published on 23 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-65908 and fix it if it is affected.\n\nWhat it is: CVE-2026-65908 is a high-severity code injection vulnerability in JetBrains PyCharm, published on 23 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-65908 in the wild and no public exploit code.\n\nAffected product: JetBrains PyCharm. 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-65908/ (Markdown: https://insights.sbomify.com/CVE-2026-65908/index.md)","id":"CVE-2026-65908","markdown":"https://insights.sbomify.com/CVE-2026-65908/index.md","name":"CVE-2026-65908","record":{"aliases":["GHSA-2j8g-fr3j-fp7c"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"JetBrains PyCharm IDE","requires_auth":"none","summary":"Attackers can execute arbitrary code by tricking users into opening a malicious Python project in PyCharm.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"JetBrains","cpe":[{"product":"pycharm","vendor":"jetbrains"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-829","name":"Inclusion of Functionality from Untrusted Control Sphere"}],"description":"In JetBrains PyCharm before 2026.1.4, 2026.2 arbitrary code execution via malicious Python executable was possible on untrusted project open","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Code injection in PyCharm","id":"CVE-2026-65908","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"DOMPurify before 3.4.0 XSS via ADD_ATTR/ADD_TAGS State Leakage","id":"CVE-2026-65911"},"packages":[],"prev":{"headline":"Code injection in TeamCity","id":"CVE-2026-65907"},"products":["PyCharm"],"published":"2026-07-23","related":[{"cvss_score":8.4,"headline":"Missing authorization in PyCharm","id":"CVE-2026-75060","kev_date_added":null,"published":"2026-08-17"},{"cvss_score":8.2,"headline":"Cross-site scripting in PyCharm","id":"CVE-2026-25847","kev_date_added":null,"published":"2026-02-09"},{"cvss_score":7.8,"headline":"Code injection in n/a","id":"CVE-2021-30005","kev_date_added":null,"published":"2021-05-11"},{"cvss_score":7.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2020-11694","kev_date_added":null,"published":"2020-04-10"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2019-14958","kev_date_added":null,"published":"2019-10-02"},{"cvss_score":6.9,"headline":"Code injection in Rider","id":"CVE-2022-29821","kev_date_added":null,"published":"2022-04-28"}],"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-24","vendors":["JetBrains"]},"summary":"Attackers can execute arbitrary code by tricking users into opening a malicious Python project in PyCharm.","url":"https://insights.sbomify.com/CVE-2026-65908/"}