Is CVE-2026-73294 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-73294 being exploited in the wild.

How severe is CVE-2026-73294?

Critical severity, with a CVSS score of 9.9, published 12 August 2026.

Which products and versions are affected?

github.com/semaphoreui/semaphore (Go) < 0.0.0-20260704181911-7e8a9434bd81, SEMVER:introduced=0,fixed=0.0.0-20260704181911-7e8a9434bd81.

Is there a fix for CVE-2026-73294?

Yes. github.com/semaphoreui/semaphore (Go): upgrade to 0.0.0-20260704181911-7e8a9434bd81 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-73294 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-73294?

Check whether you run github.com/semaphoreui/semaphore (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-73294: Semaphore UI OS command injection in git repository handling

Q: Is there a fix for CVE-2026-73294?

Yes. github.com/semaphoreui/semaphore (Go): upgrade to 0.0.0-20260704181911-7e8a9434bd81 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-73294 attacked?

It is attacked over the network, in a hosted service.

Q: Am I affected by CVE-2026-73294?

Check whether you run github.com/semaphoreui/semaphore (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-73294 · Severity: critical · CVSS 9.9 · Published 2026-08-12

Semaphore UI is a continuous delivery automation platform used to orchestrate and execute deployment workflows. An authenticated attacker holding a project manager or owner role can inject arbitrary commands via a malicious repository URL. These commands execute inside the main server process, bypassing any isolation that remote runners would normally provide, and can access sensitive data including encryption keys and project secrets.

Technologies: github.com/semaphoreui/semaphore (Go). Vendors: Go.

Quick answers

Is CVE-2026-73294 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-73294 being exploited in the wild.
How severe is CVE-2026-73294?: Critical severity, with a CVSS score of 9.9, published 12 August 2026.
Which products and versions are affected?: github.com/semaphoreui/semaphore (Go) < 0.0.0-20260704181911-7e8a9434bd81, SEMVER:introduced=0,fixed=0.0.0-20260704181911-7e8a9434bd81.
Is there a fix for CVE-2026-73294?: Yes. github.com/semaphoreui/semaphore (Go): upgrade to 0.0.0-20260704181911-7e8a9434bd81 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-73294 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-73294?: Check whether you run github.com/semaphoreui/semaphore (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/semaphoreui/semaphore (Go): upgrade to 0.0.0-20260704181911-7e8a9434bd81 or later
```
go get github.com/semaphoreui/semaphore@v0.0.0-20260704181911-7e8a9434bd81
```

Technical details

The vulnerability is an OS command injection via argument injection in git command construction. Semaphore accepts user-controlled git_url input from the HTTP POST /api/project/{id}/repositories endpoint without validating it for git option injection (unlike the git_branch field which rejects leading hyphens). The git_url is passed directly to exec.Command("git") in CmdGitClient.GetLastRemoteCommitHash without a -- argument separator. An attacker supplies a crafted git_url such as "--upload-pack=<malicious_cmd>;true", which git interprets as an option rather than a repository URL. The git command then executes the payload via shell invocation. Exploitation requires: (1) authenticated account, (2) Manager or Owner role on a project, (3) creation of a repository and schedule tied to that repository. The command executes in the schedule pool running within the main server process, independent of remote runner configuration. Patch version 0.0.0-20260704181911-7e8a9434bd81 addresses this issue.

Affected products

Semaphore UI Semaphore < 0.0.0-20260704181911-7e8a9434bd81

Identifiers

CVE-2026-73294
GHSA-xp7j-h7jc-4w8p
GO-2026-6435

Timeline

2026-09-08: disclosed: GitHub Security Advisory published
2026-07-04: patched: Patch version 0.0.0-20260704181911-7e8a9434bd81 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.