CVE-2026-73294

CRITICALPre-NVD 9.99.9
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 63% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
9.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.9Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.9
EG Score
9.9(medium)
EG Risk
61(Track*)
EG Risk 61/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity99% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 12, 2026

Advisory Details (5)

Auto-updated Aug 26, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

semaphoreUI v2.18.13 OS Command Injection - Critical vulnerability · Advisory · semaphoreui/semaphore · GitHub

https://github.com/semaphoreui/semaphore/security/advisories/GHSA-xp7j-h7jc-4w8p
generic

GitHub - semaphoreui/semaphore at v2.19.5-beta2 · GitHub

https://github.com/semaphoreui/semaphore/tree/v2.19.5-beta2
generic

GitHub - semaphoreui/semaphore at v2.18.17 · GitHub

https://github.com/semaphoreui/semaphore/tree/v2.18.17
github_commit

commit a7a7a33a64ae (semaphoreui/semaphore)

Fix landed in semaphoreui/semaphore commit a7a7a33a64ae — awaiting tagged release

https://github.com/semaphoreui/semaphore/commit/a7a7a33a64aea382a0726b3722856f298663eacf
github_commit

commit 7e8a9434bd81 (semaphoreui/semaphore)

Fix landed in semaphoreui/semaphore commit 7e8a9434bd81 — awaiting tagged release

https://github.com/semaphoreui/semaphore/commit/7e8a9434bd81b82cf42220151c74801ea97542d6

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 38× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 05:37 UTCEG score recompute
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-29 08:37 UTCEG score recompute
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-27 19:37 UTCEG score recompute
  6. 2026-08-27 14:25 UTCEPSS rescore
  7. 2026-08-26 18:49 UTCEG score recompute
  8. 2026-08-26 14:47 UTCEPSS rescore
  9. 2026-08-25 15:59 UTCEG score recompute
  10. 2026-08-25 13:49 UTCEPSS rescore
  11. 2026-08-24 17:56 UTCEG score recompute
  12. 2026-08-24 13:32 UTCEG score recompute
  13. 2026-08-23 02:09 UTCEG score recompute
  14. 2026-08-23 00:19 UTCEPSS rescore
  15. 2026-08-22 04:04 UTCEG score recompute
  16. 2026-08-21 23:49 UTCEPSS rescore
  17. 2026-08-21 01:36 UTCEG score recompute
  18. 2026-08-20 22:56 UTCEPSS rescore
  19. 2026-08-19 18:36 UTCEG score recompute
  20. 2026-08-19 17:04 UTCEPSS rescore
  21. 2026-08-18 15:13 UTCEG score recompute
  22. 2026-08-18 13:49 UTCEPSS rescore
  23. 2026-08-18 13:49 UTCEPSS rescore
  24. 2026-08-17 16:39 UTCEG score recompute
  25. 2026-08-17 13:47 UTCEPSS rescore
Show 13 more
  1. 2026-08-16 18:34 UTCEG score recompute
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 05:20 UTCEG score recompute
  5. 2026-08-16 02:15 UTCEPSS rescore
  6. 2026-08-15 02:54 UTCEG score recompute
  7. 2026-08-15 01:31 UTCEPSS rescore
  8. 2026-08-14 00:28 UTCEG score recompute
  9. 2026-08-13 22:00 UTCEPSS rescore
  10. 2026-08-12 17:35 UTCEG score recompute
  11. 2026-08-12 16:21 UTCEG score recompute
  12. 2026-08-12 16:01 UTCEG score recompute
  13. 2026-08-12 16:00 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-73294?
CVE-2026-73294 is a critical vulnerability published on August 12, 2026. 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,…
When was CVE-2026-73294 disclosed?
CVE-2026-73294 was first published in the National Vulnerability Database on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73294 actively exploited?
CVE-2026-73294 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 62.8% of all scored CVEs.
What is the CVSS score of CVE-2026-73294?
CVE-2026-73294 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-73294?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73294, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-73294

Explore →

Is Your Infrastructure Affected by CVE-2026-73294?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.