LiveActive security incident?Get immediate response
CVE Record

CVE-2026-73294: Semaphore U: OS Command Injection

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.

CriticalCVSS 9.9Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A logged-in Semaphore project Manager or Owner can abuse a repository URL setting to run operating-system commands on the Semaphore server. Successful exploitation could expose secrets, alter automation, disrupt service, or enable broader compromise under the server process’s permissions.

Executive priority

Treat remediation as urgent, especially where Semaphore manages sensitive infrastructure, credentials, or production automation. Prioritize exposed deployments and environments with multiple Managers or Owners. Upgrade promptly, restrict privileged project access until completion, and investigate suspicious repository changes or server activity.

Technical view

Affected Semaphore versions pass an attacker-controlled --upload-pack option from repository git_url handling into CmdGitClient.GetLastRemoteCommitHash. The path is reachable through POST /api/project/{id}/repositories and scheduled commit-hash polling, causing OS command injection in the Semaphore server process. The issue maps to CWE-78 and CWE-88.

Likely exposure

Exposure exists on Semaphore versions below 2.18.17 and versions from 2.19.0-alpha3 through 2.19.5-beta1. Exploitation requires authenticated project Manager or Owner privileges. Internet accessibility, broadly assigned project roles, and untrusted repository configuration increase risk.

Exploitation context

The CVSS 3.1 score is 9.9 because exploitation is network-accessible, low-complexity, requires limited privileges, and can affect confidentiality, integrity, and availability. The bundle reports no KEV listing and provides no evidence of active exploitation; real-world exploitation status is therefore unconfirmed.

Researcher notes

The vulnerable data flow connects attacker-controlled repository configuration to a Git command option processed by CmdGitClient.GetLastRemoteCommitHash. Scheduled polling may trigger the unsafe path after configuration. The supplied advisory and commits support the root cause and fixed versions, but the bundle does not establish public proof-of-concept availability or exploitation in the wild.

Mitigation direction

  • Upgrade stable deployments to Semaphore 2.18.17 or later.
  • Upgrade prerelease deployments to 2.19.5-beta2 or later.
  • Until upgraded, restrict project Manager and Owner roles to trusted administrators.
  • Review vendor guidance before applying additional compensating controls.

Validation and detection

  • Inventory Semaphore versions and identify every deployment within the affected ranges.
  • Confirm upgraded instances report 2.18.17, 2.19.5-beta2, or a later version.
  • Review repository git_url values for suspicious --upload-pack options or unexpected content.
  • Examine Semaphore server and process logs for unexplained command execution or anomalous child processes.
  • Verify project Manager and Owner assignments follow least privilege.
Prepared
Confidence
high
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-78: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · medium confidence lookup

CWE-88: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-73294 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.9CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16GitHub_M

Vulnerability scoring details

Base CVSS 3.1 score

9.9Critical
CVSS 3.1 vector shape for CVE-2026-73294Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
semaphoreuisemaphore< 2.18.17, >= 2.19.0-alpha3, < 2.19.5-beta2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.