CVE-2025-51387: GitKraken Desktop · Code Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 4 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
Immediate mitigation steps include disabling the RunAsNode setting and ensuring EnableNodeCliInspectArguments is explicitly disabled in the Electron Fuse configuration of GitKraken Desktop. Since these settings are typically controlled by the application vendor, affected organizations should monitor for and apply official patches or updates from GitKraken as soon as they become available. In the interim, organizations should restrict network access to developer workstations running vulnerable GitKraken versions, implement application whitelisting to prevent unauthorized execution of Node.js processes, and enforce strict endpoint security controls including behavior-based detection for suspicious command-line arguments or process launches. Additionally, organizations should audit developer environments for signs of compromise and review source code repositories for unauthorized changes. Educating developers about the risks of running untrusted code and maintaining robust backup and version control practices will also help mitigate potential damage. Finally, consider isolating development environments from critical production networks to limit lateral movement in case of exploitation.
Description
The GitKraken Desktop 10.8.0 and 11.1.0 is susceptible to code injection due to misconfigured Electron Fuses. Specifically, the following insecure settings were observed: RunAsNode is enabled and EnableNodeCliInspectArguments is not disabled. These configurations allow the application to be executed in Node.js mode, enabling attackers to pass arguments that result in arbitrary code execution.