GitAhead up to 2.7.1 Show in Finder command injection

Summaryinfo

A vulnerability identified as critical has been detected in GitAhead up to 2.7.1. Impacted is an unknown function of the component Show in Finder. Performing a manipulation results in command injection. This vulnerability is cataloged as CVE-2026-106059. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in GitAhead up to 2.7.1. It has been classified as critical. This affects some unknown functionality of the component Show in Finder. The manipulation with an unknown input leads to a command injection vulnerability. CWE is classifying the issue as CWE-77. The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-106059 since 10/06/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/07/2026). MITRE ATT&CK project uses the attack technique T1202 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• GitAhead

Version

• 2.7.0
• 2.7.1

Website

• Product: https://github.com/gitahead/gitahead/

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion