Skip to main content

GitAhead CVE-2026-106059

| EUVDEUVD-2026-94307 HIGH
OS Command Injection (CWE-78)
2026-10-07 VulnCheck GHSA-3g7h-c55x-cx2v
8.7
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Attacker crafts repo filename with quote + do-shell-script payload
  2. Delivery
    Victim clones/opens repository in GitAhead on macOS
  3. Exploit
    Victim selects Show in Finder on the file
  4. Execution
    Unescaped path breaks out of AppleScript string
  5. Impact
    Arbitrary shell commands execute as victim user

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization OS command sanitization, avoid shell exec
MITRE ATT&CK

2 techniques across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires that the victim run GitAhead (version ≤2.7.1) on macOS, open/clone a repository under attacker control containing a file whose path includes a double quote plus an AppleScript do shell script payload, and then actively invoke the 'Show in Finder' action on that file - this user interaction (UI:P) is the primary limiting factor. The root cause is unescaped interpolation of the repository filename into the Show in Finder AppleScript (ShowTool.cpp). No application authentication is required (PR:N), and the default build is vulnerable, but the flaw cannot trigger without the victim's deliberate menu action and does not affect non-macOS platforms since it relies on AppleScript.

Impact

The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H, score 8.7) is internally consistent with the description: an attacker needs no authentication to GitAhead and no special conditions, but exploitation is gated by passive user interaction (UI:P) - the victim must choose 'Show in Finder' on an attacker-controlled file. This is a classic 'malicious repository' client-side vector rather than a remotely-triggerable server flaw, so real-world risk depends on social engineering (getting a developer to clone a hostile repo and interact with it). No EPSS score, KEV listing, or public POC was provided in the input, so there is no signal of active exploitation or automated weaponization; the technical impact is high (arbitrary shell execution as the victim user) but the delivery is user-dependent and the product is a discontinued niche developer tool. Net assessment: a genuine high-severity code-execution bug worth patching/migrating off GitAhead for affected macOS users, but not a mass-exploitation emergency - closer to a targeted-threat profile given the user-interaction requirement and absence of exploitation telemetry. Note the AT:N/AV:N combination describes network-origin malicious content, not a network service; verify this framing matches how your environment distributes repositories.

Exploit ScenarioDerived

An attacker publishes or contributes to a Git repository containing a file whose path embeds a double quote followed by a do shell script AppleScript payload. A macOS victim clones or opens that repository in GitAhead (through 2.7.1) and selects 'Show in Finder' on the file, causing the unescaped path to break out of the AppleScript string and execute arbitrary shell commands as the victim user. No public exploit was identified in the provided data, but the technique is fully described in the VulnCheck advisory and the vulnerable code is pinpointed in ShowTool.cpp.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 1.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 07, 2026

Command injection in GitAhead 2.7.1 and earlier on macOS allows an attacker to execute arbitrary shell commands as the victim user by placing a crafted filename containing a double quote and AppleScript payload into a repository and convincing the victim to select 'Show in Finder' on that file. The flaw requires user interaction (the victim must open an attacker-controlled repository and explicitly trigger the action) and affects only macOS; no public exploit code or active exploitation has been identified at time of analysis. The CVSS 4.0 score is 8.7 with a vector indicating network attack, no privileges required, and passive user interaction.

RemediationAI

No vendor-released patch is identified in the available data at time of analysis. As a compensating control, users on macOS should avoid using the 'Show in Finder' feature on files from untrusted repositories; opening untrusted repositories in GitAhead should be avoided entirely if the feature cannot be disabled. Alternatively, before invoking 'Show in Finder', manually inspect repository filenames for embedded double quotes or AppleScript-like payloads, but this is error-prone and not a reliable defense. Monitoring the GitHub issue #663 for a future patched release is recommended. Until a fix is available, consider running GitAhead in a restricted sandbox or with limited user privileges to reduce the impact of successful exploitation.

Affected VersionsENISA

GitAhead 0 ≤2.7.1

Affected Packages

euvd gitahead no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

GitAhead is a cross-platform Git client written in C++/Qt. The vulnerability resides in src/tools/ShowTool.cpp (lines 40-48) where the file path of a repository entry is interpolated unescaped into an AppleScript string that is executed via macOS's osascript. Because the filename is not sanitized, a filename containing a double quote followed by do shell script and an arbitrary command breaks out of the intended string context and causes the shell command to run with the privileges of the GitAhead user. This is a classic OS command injection (CWE-78). The affected CPE is cpe:2.3:a:gitahead:gitahead:*:*:*:*:*:*:*:* (all versions up to and including 2.7.1). The attack vector is network-based because the malicious repository can be cloned from a remote source, and no authentication to GitAhead is required (PR:N), but exploitation is gated by passive user interaction (UI:P) - the victim must actively choose 'Show in Finder' on the malicious file. Non-macOS platforms do not use AppleScript in this code path and are therefore not affected.

Know when Gitahead gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 8.7 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 8.8 HIGH

Malicious repo content is network-delivered (AV:N) and reliably exploitable (AC:L) with no app auth (PR:N), but requires the victim to choose Show in Finder (UI:R); shell execution yields full C/I/A:H.

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
Passive
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

GitAhead through 2.7.1 on macOS contains a command injection vulnerability that allows attackers to execute shell commands by crafting repository filenames interpolated unescaped into the Show in Finder AppleScript. Attackers can commit a file whose path contains a double quote followed by a do shell script payload, which runs as the victim user when Show in Finder is chosen.

Executive ViewAI

Why It Matters

GitAhead 2.7.1 and earlier on macOS contains a command injection flaw that allows an attacker to run arbitrary shell commands with the rights of the logged-in user once a developer opens a repository from an untrusted source and selects 'Show in Finder' on a specially named file; the issue is unauthenticated but depends on that user interaction. Because the affected population is macOS developers - accounts that typically hold source code, repository credentials, and access to build and deployment pipelines - a successful compromise could expose intellectual property and provide a foothold for lateral movement into engineering systems. No vendor patch is currently available, so leadership should treat exposure as an open risk requiring interim controls rather than a resolved finding.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: uninstall or block GitAhead 2.7.1 and earlier via MDM and application allowlisting; restrict use to trusted repositories and prohibit 'Show in Finder' on files from untrusted sources; deploy EDR alerting on osascript or shell processes spawned by GitAhead; enforce least-privilege developer accounts and scoped repository credentials; and monitor the vendor advisory for a patched release.

Threat Intelligence Overview

EPSS Score
1.3%
Top 31% exploitable
Prevalence
Low
niche, discontinued macOS Git GUI client for developers
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 1.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

45
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

OS command injection occurs when an application passes unsanitized user input directly into system shell commands.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy