{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-43899 exists.","fix":"No fix has been published for CVE-2026-43899 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-43899 is a critical code injection vulnerability in ThinkInAIXYZ deepchat, published on 11 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-43899 and fix it if it is affected.\n\nWhat it is: CVE-2026-43899 is a critical code injection vulnerability in ThinkInAIXYZ deepchat, published on 11 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-43899 exists.\n\nAffected product: ThinkInAIXYZ deepchat. 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-43899/ (Markdown: https://insights.sbomify.com/CVE-2026-43899/index.md)","id":"CVE-2026-43899","markdown":"https://insights.sbomify.com/CVE-2026-43899/index.md","name":"CVE-2026-43899","record":{"aliases":["GHSA-cp8j-jx7q-7r5f"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"AI agent platform","requires_auth":"none","summary":"Attackers can execute arbitrary code by bypassing URL validation in native window handlers via malicious Markdown links in DeepChat.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.6,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"DeepChat is an open-source artificial intelligence agent platform that unifies models, tools, and agents. Prior to v1.0.4-beta.1, An incomplete mitigation for CVE-2025-55733 leaves DeepChat vulnerable to an arbitrary protocol execution bypass (RCE). While the patch correctly restricted api.openExternal() inside the renderer's preload/index.ts script, it structurally neglected to sanitize native Electron pop-up window handlers. An attacker or a compromised AI endpoint returning a Markdown link can trigger a target=\"_blank\" native window interception in tabPresenter.ts, which forwards the malicious URL directly to shell.openExternal(url) and completely bypasses the isValidExternalUrl security boundary. This vulnerability is fixed in v1.0.4-beta.1.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Code injection in deepchat","id":"CVE-2026-43899","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":"DeepChat: Persistent DOM XSS via HTML Entity Encoding in `\u003cantArtifact\u003e` SVG Rendering (Bypass of `svgSanitizer.ts`)","id":"CVE-2026-43900"},"packages":[],"prev":{"headline":"SandboxJS: Sandbox escape via Function.caller leakage of internal call op","id":"CVE-2026-43898"},"products":["deepchat"],"published":"2026-05-11","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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-12","vendors":["ThinkInAIXYZ"]},"summary":"Attackers can execute arbitrary code by bypassing URL validation in native window handlers via malicious Markdown links in DeepChat.","url":"https://insights.sbomify.com/CVE-2026-43899/"}