CVE-2025-51387
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGitKraken Desktop 10.8.0 and 11.1.0 contains insecure Electron Fuses configuration where RunAsNode is enabled and EnableNodeCliInspectArguments is not disabled. These settings allow the application to be spawned in Node.js mode, enabling attackers to inject arbitrary code execution arguments via the command line.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 10.8.0= 11.1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm GitKraken Desktop installationLocate the GitKraken executable in your system - common paths include C:\Program Files\GitKraken\gitkraken.exe on Windows or /Applications/GitKraken.app on macOS. Use 'where gitkraken' on Windows or 'mdfind "kMDItemCFBundleIdentifier == \"com.axosoft.gitkraken\""' on macOS.Affected if GitKraken Desktop is installed on the system.
-
Identify installed versionRun 'gitkraken --version' from command line, or right-click the executable, select Properties, and check the File version/Product version details. On macOS, use 'defaults read /Applications/GitKraken.app/Contents/Info.plist CFBundleVersion'.Affected if The installed version is exactly 10.8.0 or 11.1.0.
-
Verify Electron fuses configuration (advanced)Extract the application asar archive from resources folder and inspect the Electron binary using 'fuses-v1 extractor' or similar tool that can read Electron fuse states from the compiled binary. Check for RunAsNode fuse being ON and EnableNodeCliInspectArguments fuse not being disabled.Affected if The Electron fuses show RunAsNode is enabled and EnableNodeCliInspectArguments is not disabled.
If GitKraken Desktop version 10.8.0 or 11.1.0 is installed, the environment is affected by this insecure Electron Fuses configuration.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedDisable RunAsNode and EnableNodeCliInspectArguments in Electron Fuses configuration at build time, then rebuild and redistribute the application.
Latest GitKraken Desktop version (beyond 11.1.0)
- Upgrade GitKraken Desktop to the latest available version beyond 11.1.0
- Verify the upgrade completed successfully by checking Help > About GitKraken
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-51387 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-51387 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data