Semaphoreui Semaphore up to 2.18.16/2.19.5-beta1 Git Repository GetLastRemoteCommitHash upload-pack os command injection

Summaryinfo

A vulnerability has been found in Semaphoreui Semaphore up to 2.18.16/2.19.5-beta1 and classified as problematic. Affected is the function GetLastRemoteCommitHash of the component Git Repository Handler. Performing a manipulation of the argument upload-pack results in os command injection. This vulnerability is identified as CVE-2026-73294. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Semaphoreui Semaphore up to 2.18.16/2.19.5-beta1. This affects the function GetLastRemoteCommitHash of the component Git Repository Handler. The manipulation of the argument upload-pack with an unknown input leads to a os command injection vulnerability. CWE is classifying the issue as CWE-78. The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS 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:

Semaphore UI is a web interface for managing DevOps tools. Prior to 2.18.17 and 2.19.5-beta2, repository git_url handling passes an attacker-controlled --upload-pack option to CmdGitClient.GetLastRemoteCommitHash through POST /api/project/{id}/repositories and scheduled commit-hash polling, allowing a project Manager or Owner to execute arbitrary OS commands in the Semaphore server process. This issue is fixed in versions 2.18.17 and 2.19.5-beta2.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-73294 since 08/11/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. The exploitation needs additional levels of successful authentication. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1202 according to MITRE ATT&CK.

Upgrading to version 2.18.17 or 2.19.5-beta2 eliminates this vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• Semaphoreui

Name

• Semaphore

Version

• 2.18.0
• 2.18.1
• 2.18.2
• 2.18.3
• 2.18.4
• 2.18.5
• 2.18.6
• 2.18.7
• 2.18.8
• 2.18.9
• 2.18.10
• 2.18.11
• 2.18.12
• 2.18.13
• 2.18.14
• 2.18.15
• 2.18.16
• 2.19.5-beta1

Website

• Product: https://github.com/semaphoreui/semaphore/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion