CVE-2026-73294: semaphoreui semaphore · OS Command Injection
Affects semaphoreui semaphoreSource CVE Database V5
Not known to be exploited · CVSS 9.9 Critical : upgrade to 2.19.5-beta2 or 2.18.17 as a priority.
Data as of 10 Nov 2026, 23:24 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.19.5-beta2, 2.18.17
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade semaphore to 2.19.5-beta2 or 2.18.17; semaphoreui/semaphore to 2.18.17.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| semaphoreuisemaphore | Affected
| Fixed in
|
| semaphoreuisemaphore | Affected
| Fixed in
|
GitHubsemaphoreui/semaphorepkg:github/semaphoreui/semaphoreOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in Semaphore UI versions 2.18.17 and 2.19.5-beta2. Users should upgrade to at least these versions to remediate the issue. No vendor advisory content is provided to indicate alternative mitigations or temporary fixes. Patch status is confirmed by the version information in the description.
Description
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.
References
- github.com/semaphoreui/semaphore/security/advisories/GHSA-xp7j-h7jc-4w8p (opens in a new tab)
- github.com/semaphoreui/semaphore/commit/7e8a9434bd81b82cf42220151c74801ea97542d6 (opens in a new tab)
- github.com/semaphoreui/semaphore/commit/a7a7a33a64aea382a0726b3722856f298663eacf (opens in a new tab)
- github.com/semaphoreui/semaphore/tree/v2.18.17 (opens in a new tab)
- github.com/semaphoreui/semaphore/tree/v2.19.5-beta2 (opens in a new tab)