Advisories
This weekExploitable · Confirmed

github.com/semaphoreui/semaphore: Semaphore UI: Manager-to-owner privilege escalation via custom-role slug collision

There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.

Does it affect what I run?

github.com/semaphoreui/semaphore (Go)

Checked in your browser. The version you type is not sent anywhere.

Who is affected

  • github.com/semaphoreui/semaphore (Go): every version, before 0.0.0-20260705182501-bb2a4e1f08c8
  • github.com/semaphoreui/semaphore (Go): every version, before 0.0.0-20260705182501-bb2a4e1f08c8

The fix

  • github.com/semaphoreui/semaphore (Go) fixed in 0.0.0-20260705182501-bb2a4e1f08c8

    go
    go get github.com/semaphoreui/semaphore@v0.0.0-20260705182501-bb2a4e1f08c8
    Check what is installed
    go list -m github.com/semaphoreui/semaphore
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Go dependency github.com/semaphoreui/semaphore to 0.0.0-20260705182501-bb2a4e1f08c8 or the nearest later release, to fix CVE-2026-73293. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.

Fix commands generated from the advisory's versions. No model wrote them.

In plain words

Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.

Evidence

Timeline

  1. First published here, as "For your digest".
  2. Level changed from "For your digest" to "This week".
  3. Evidence added: CISA's assessment in the CVE record says a proof of concept is public. (CISA Vulnrichment (SSVC and KEV fields inside CVE records))