# CVE-2026-73293: Semaphore UI: Manager-to-owner privilege escalation via custom-role slug collision

> A project manager can escalate privileges to owner level by creating a custom role with specific permissions, bypassing intended access controls.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-cxvf-gvfq-36w2, GO-2026-6371

## What is CVE-2026-73293?

CVE-2026-73293 is a high-severity vulnerability in semaphoreui semaphore, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Semaphore UI is a web interface for managing DevOps tools.  Prior to 2.18.19 and from 2.19.0-alpha3 until 2.19.5-beta5, ProjectMiddleware and GetProjectOrGlobalRoleBySlug allow a project manager to use POST /api/project/{id}/roles to create a custom manager role with permission bitmask 15, overriding the built-in manager permissions and granting CanUpdateProject and CanManageProjectUsers owner capabilities. This issue is fixed in versions 2.18.19 and 2.19.5-beta5.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-73293?

3 open source packages ship an affected version, including github.com/semaphoreui/semaphore.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/semaphoreui/semaphore` | Go | All versions | 0.0.0-20260705182501-bb2a4e1f08c8 |
| `github.com/semaphoreui/semaphore` | Go | All versions | 0.0.0-20260705182501-bb2a4e1f08c8 |
| `github.com/semaphoreui/semaphore` | Go | All versions | 0.0.0-20260705182501-bb2a4e1f08c8 |

## How do I fix CVE-2026-73293?

Upgrade github.com/semaphoreui/semaphore to 0.0.0-20260705182501-bb2a4e1f08c8 or later.

## Is CVE-2026-73293 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73293 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-73293 and fix it if it is affected.

What it is: CVE-2026-73293 is a high-severity vulnerability in semaphoreui semaphore, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73293 exists.

Affected packages and fixed versions:
- github.com/semaphoreui/semaphore (Go): affected all versions; fixed in 0.0.0-20260705182501-bb2a4e1f08c8
- github.com/semaphoreui/semaphore (Go): affected all versions; fixed in 0.0.0-20260705182501-bb2a4e1f08c8
- github.com/semaphoreui/semaphore (Go): affected all versions; fixed in 0.0.0-20260705182501-bb2a4e1f08c8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-73293/ (Markdown: https://insights.sbomify.com/CVE-2026-73293/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-73293
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-73293
- OSV: https://osv.dev/vulnerability/CVE-2026-73293

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-73293/
Summaries are generated and may contain mistakes; the official description above is the record.