{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93425 exists.","fix":"No fix has been published for CVE-2026-93425 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-93425 is a critical command injection vulnerability in dokploy, published on 24 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-93425 and fix it if it is affected.\n\nWhat it is: CVE-2026-93425 is a critical command injection vulnerability in dokploy, published on 24 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93425 exists.\n\nAffected product: dokploy. 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-93425/ (Markdown: https://insights.sbomify.com/CVE-2026-93425/index.md)","id":"CVE-2026-93425","markdown":"https://insights.sbomify.com/CVE-2026-93425/index.md","name":"CVE-2026-93425","record":{"aliases":["GHSA-56g6-wjr4-5q7p"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Dokploy PaaS","requires_auth":"low_privilege","summary":"Authenticated users can inject shell commands via repoPath to execute arbitrary code as root, potentially compromising the host via Docker socket access.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.9,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.29.13, the patch.readRepoDirectories tRPC procedure passes the user-controlled repoPath value from apps/dokploy/server/api/routers/patch.ts into a shell command in packages/server/src/services/patch-repo.ts without safe argument quoting. An authenticated organization member with service:read permission can inject shell metacharacters into repoPath and execute arbitrary commands through child_process.exec as root in the Dokploy container. The supplied service identifier is used only to resolve the server and does not constrain repoPath. Because the standard deployment mounts /var/run/docker.sock, container-root command execution can be used to control Docker and compromise the host and its managed applications. This issue is fixed in version 0.29.13.","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":"Dokploy: Authenticated OS Command Injection in patch.readRepoDirectories (repoPath) leads to RCE as root","id":"CVE-2026-93425","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"SigNoz 0.87.0 before 0.142.0 - SQL Injection in v5 Query Builder Field Key Names","id":"CVE-2026-93426"},"packages":[],"prev":{"headline":"Mesop: Unauthenticated ANSI Escape Sequence Injection in CSP Reporting Endpoint","id":"CVE-2026-93421"},"products":["dokploy"],"published":"2026-09-24","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-09-24","vendors":["Dokploy"]},"summary":"Authenticated users can inject shell commands via repoPath to execute arbitrary code as root, potentially compromising the host via Docker socket access.","url":"https://insights.sbomify.com/CVE-2026-93425/"}