Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.9amended

Semaphore U: OS Command Injection

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

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/semaphoreui/semaphore 0.0.0-20260704181911-7e8a9434bd81), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.9 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
  • CVE-2026-73294: 0.65% estimated exploitation activity in the next 30 days; percentile 51.19 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary An OS command injection in repository giturl handling lets any user holding the Manager or Owner role on any project (the normal project-collaborator roles) achieve remote code execution on the Semaphore server host. Using git's --upload-pack=<cmd option, an attacker runs arbitrary commands. The command executes inside the main Semaphore server process (via the schedule commit-hash poller), so it runs even when jobs are configured for remote runners — bypassing runner isolation and exposing the master encryption key and every project's secrets. Reproducible on a default install (gitclient: cmdgit); no non-default configuration is required. Details The repository giturl is attacker-controlled (HTTP body) and reaches exec.Command("git", ...) unvalidated. Two missing controls cause this: 1. giturl is never validated against option injection. Repository.Validate() (db/Repository.go, ~lines 138–156) validates the branch via ValidateGitBranch (db/gitbranch.go, which rejects a…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-xp7j-h7jc-4w8p

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6435

  3. Revision 1 · created ·

    Published from osv record GHSA-xp7j-h7jc-4w8p

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-73294

Advisory: Semaphore U: OS Command Injection
IDs: CVE-2026-73294, GHSA-xp7j-h7jc-4w8p
Record: https://patchnext.com/advisories/cve-2026-73294 (revision 3, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/semaphoreui/semaphore 0.0.0-20260704181911-7e8a9434bd81. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/semaphoreui/semaphore: affected < 0.0.0-20260704181911-7e8a9434bd81; fixed in 0.0.0-20260704181911-7e8a9434bd81

## Suggested inspection (read-only)
- Go github.com/semaphoreui/semaphore: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/semaphoreui/semaphore.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-xp7j-h7jc-4w8p (OSV record GHSA-xp7j-h7jc-4w8p lists affected ranges: Go github.com/semaphoreui/semaphore >=0 <0.0.0-20260704181911-7e8a9434bd81 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6435 (OSV record GO-2026-6435 lists affected ranges: Go github.com/semaphoreui/semaphore >=0 <0.0.0-20260704181911-7e8a9434bd81 (fixed))
- Verified: https://github.com/advisories/GHSA-xp7j-h7jc-4w8p (GitHub-reviewed advisory GHSA-xp7j-h7jc-4w8p lists affected ranges: Go github.com/semaphoreui/semaphore >=0 <0.0.0-20260704181911-7e8a9434bd81)

Commands are suggestions: review each one before running it.

Loading voting…