CVE-2025-51387
BaseFortify
Publication date: 2025-08-04
Last updated on: 2025-10-09
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| axosoft | gitkraken_desktop | 10.8.0 |
| axosoft | gitkraken_desktop | 11.1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-94 | The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-51387 is a vulnerability in GitKraken Desktop versions 10.8.0 and 11.1.0 caused by misconfigured Electron Fuses, specifically 'runAsNode' being enabled and 'enableNodeCliInspectArguments' not disabled. These settings allow the application to run in Node.js mode, enabling an attacker who already has access to the system to execute arbitrary code within the Electron app context. This does not enable remote code execution by itself but can be abused to escalate privileges or perform actions with the app's permissions. [1]
How can this vulnerability impact me? :
If exploited by an attacker who already has access to your system, this vulnerability allows them to execute arbitrary code within the Electron app, potentially using the app's permissions to access sensitive data or perform privileged actions. For example, an attacker could use the app to access address books or other protected resources on macOS, effectively escalating their control and performing 'living off the land' attacks. This can lead to data theft, privacy breaches, or further system compromise. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect if an Electron app is vulnerable by using the tool 'electroniz3r' on macOS. Specifically, the 'verify' subcommand checks if a specified Electron app is vulnerable to code injection by starting a debug WebSocket server within the target app and reporting its vulnerability status. For example, running `electroniz3r verify --app-path /path/to/app` will indicate if the app is vulnerable. [2]
What immediate steps should I take to mitigate this vulnerability?
The recommended immediate mitigation is to disable the 'runAsNode' Electron fuse, which controls whether the ELECTRON_RUN_AS_NODE environment variable is respected. Disabling this fuse prevents the described attack but may break functionality relying on process.fork in the main process. As an alternative, use Utility Processes for standalone Node.js processes. Additionally, follow Electron's Security Checklist for best practices. [1]