CVE-2026-73293: Semaphore UI Manager-to-owner Privilege Escalation Vulnerability
HIGHCVE-2026-73293 is a HIGH (CVSS 8.8) manager-to-owner privilege escalation vulnerability (CWE-269: Improper Privilege Management) affecting Semaphore UI libraries in the Go ecosystem. The issue involves manager-to-owner privilege escalation via custom-role slug collision. Remediation is available by upgrading affected packages to version 0.0.0-20260705182501-bb2a4e1f08c8.
CVE-2026-73293 at a Glance
Security Impact
CVSS: 8.8
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).
How to Fix CVE-2026-73293
To remediate this vulnerability, upgrade all affected Semaphore UI dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/semaphoreui/semaphore to 0.0.0-20260705182501-bb2a4e1f08c8
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/semaphoreui/semaphore
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-73293, inspect your project dependencies for Semaphore UI:
inspect dependencies for github.com/semaphoreui/semaphore
Analyze the terminal output to locate any version of Semaphore UI in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.0.0-20260705182501-bb2a4e1f08c8), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-269: Improper Privilege Management, where the product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. In Semaphore UI, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-73293 Affected Semaphore UI Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/semaphoreui/semaphore
|
Go |
< 0.0.0-20260705182501-bb2a4e1f08c8
|
0.0.0-20260705182501-bb2a4e1f08c8
|
References
Frequently Asked Questions
What is CVE-2026-73293?
Which Semaphore UI versions are affected?
What version fixes CVE-2026-73293?
Is github.com/semaphoreui/semaphore affected?
What is the CVSS score of CVE-2026-73293?
What CWE is associated with CVE-2026-73293?
How can I check Go dependencies for CVE-2026-73293?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-cxvf-gvfq-36w2",
"modified" : "2026-09-03T19:23:42Z",
"published" : "2026-09-03T19:23:42Z",
"aliases" : [ "CVE-2026-73293" ],
"summary" : "Semaphore UI: Manager-to-owner privilege escalation via custom-role slug collision",
"details" : "## Summary\n\nSemaphore resolves a project member's effective permissions in `ProjectMiddleware` by looking up a role row whose slug matches the member's assigned role, and overwrites the built-in permission bitmask with that row's value. A member holding the built-in `manager` role creates a custom project role through `POST /api/project/{id}/roles`, a route gated only by the `CanManageProjectResources` permission that `manager` already holds.\n\nThe role-creation validator does not reserve the built-in slug names (`owner`, `manager`, `task_runner`, `guest`) and sets no ceiling on the permission bits a caller may grant. A manager creates a role with slug `manager` carrying the full bitmask `15`, including the two owner-only bits `CanUpdateProject` and `CanManageProjectUsers` that `manager` does not hold. The slug lookup that backs permission resolution ignores project scope, so this attacker-created row is returned on the next request and the manager's effective permissions become owner-equivalent.\n\nResult: a project manager escalates to full owner of the project with one authenticated request, then adds or removes members, changes project settings, deletes the project, or demotes the legitimate owner.\n\n## Affected\n\nsemaphoreui/semaphore v2.18.12 (current latest as of 2026-06-09) and `develop` HEAD. Confirmed live-exploitable on v2.18.12 (commit 8a4dcf0); the affected files are unchanged on `develop` with no fix commit since the tag. Earlier releases that ship PRO custom project roles are likely affected but were not tested.\n\nRequires the PRO build (custom project roles). The official `semaphoreui/semaphore` Docker image ships this feature active by default, with no subscription or configuration flag.\n\nPure community builds without custom project roles are not affected: the role-creation endpoint returns 404 there.\n\n## Root cause\n\n`ProjectMiddleware` reads the member's built-in role permissions, then calls `GetProjectOrGlobalRoleBySlug` and, when a role row shares the member's role slug, replaces the effective permission bitmask with the database value (`api/projects/project.go:49-53`). `GetProjectOrGlobalRoleBySlug(projectID, slug)` accepts a project id but runs `select * from role where slug=?`, ignoring project scope (`db/sql/role.go:59-62`). `ValidateRole` checks only that the role name is non-empty, and enforces neither a reserved-slug list nor a permission ceiling (`db/Role.go:10-15`). The role-creation route `POST /api/project/{id}/roles` is gated by `CanManageProjectResources` (`api/router.go:294,354`), a bit the built-in `manager` role holds, while the actions it unlocks are gated by the owner-only `CanUpdateProject` and `CanManageProjectUsers` (`api/router.go:364,380`). A manager creates a row with slug `manager` and permissions `15`, and the next request resolves the manager's effective permissions to the owner bitmask.\n\n## Reproduction\n\nsemaphoreui/semaphore v2.18.12 Docker (official image, PRO build), default config, default roles.\n\n1. An admin or owner adds the attacker to a project with the built-in `manager` role; the attacker confirms the baseline, where owner-only endpoints are denied.\n\n```\nGET /api/project/42/role Cookie: semaphore=<manager-session>\n -> {\"role\":\"manager\",\"permissions\":5}\nPUT /api/project/42 Cookie: semaphore=<manager-session>\n -> HTTP/1.1 403 Forbidden\n```\n\n2. The manager creates a custom role whose slug collides with the built-in `manager` and carries every permission bit.\n\n```\nPOST /api/project/42/roles Cookie: semaphore=<manager-session>\nContent-Type: application/json\n{\"slug\":\"manager\",\"name\":\"pwn\",\"permissions\":15}\n -> HTTP/1.1 201 Created\n {\"slug\":\"manager\",\"name\":\"pwn\",\"permissions\":15,\"project_id\":42}\n```\n\n3. On the next request the manager holds the owner bitmask and performs owner-only actions.\n\n```\nGET /api/project/42/role -> {\"role\":\"manager\",\"permissions\":15}\nPUT /api/project/42 {\"id\":42,\"name\":\"owned\",\"alert\":false} -> 204 No Content\nPOST /api/project/42/users {\"user_id\":99,\"role\":\"task_runner\"} -> 204 No Content\n```\n\nLive-verified: a manager with permissions `5` obtains permissions `15` with one POST, then changes project settings and adds project members, both of which return 403 before the role is created.\n\n## Impact\n\n- Full administrative control of the project from a non-owner role: change project settings, delete the project.\n- Add, remove, and re-role project members, including granting roles the attacker should not control.\n- Removal or demotion of the legitimate project owner.\n- Reached by the project `manager` role in default config with one request; not reachable by `task_runner`, `guest`, or unauthenticated callers.\n\n## Credit\n\nJan Kahmen, [turingpoint](https://www.turingpoint.de) (jan@turingpoint.de)",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/semaphoreui/semaphore"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.0.0-20260705182501-bb2a4e1f08c8"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/semaphoreui/semaphore/security/advisories/GHSA-cxvf-gvfq-36w2"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-73293"
}, {
"type" : "WEB",
"url" : "https://github.com/semaphoreui/semaphore/commit/1c4bb65df114962134f8829d4a03667106a01a68"
}, {
"type" : "WEB",
"url" : "https://github.com/semaphoreui/semaphore/commit/bb2a4e1f08c8023e618f8dd6eaca73554f2c33bb"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/semaphoreui/semaphore"
}, {
"type" : "WEB",
"url" : "https://github.com/semaphoreui/semaphore/releases/tag/v2.18.19"
}, {
"type" : "WEB",
"url" : "https://github.com/semaphoreui/semaphore/releases/tag/v2.19.5-beta5"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-269" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-09-03T19:23:42Z",
"nvd_published_at" : "2026-08-12T16:17:22Z"
}
}