CVE-2026-73293

Semaphore UI: Manager-to-owner privilege escalation via custom-role slug collision

• Full administrative control of the project from a non-owner role: change project settings, delete the project.
• Add, remove, and re-role project members, including granting roles the attacker should not control.
• Removal or demotion of the legitimate project owner.
• Reached by the project manager role in default config with one request; not reachable by task_runner, guest, or unauthenticated callers.

The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access. Typical impact: privilege escalation beyond the intended level.

CVE-2026-73293 has a CVSS score of 8.8 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.0.0-20260705182501-bb2a4e1f08c8); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2026-73293? CVE-2026-73293 is a high-severity improper privilege management vulnerability in github.com/semaphoreui/semaphore (go), affecting versions < 0.0.0-20260705182501-bb2a4e1f08c8. It is fixed in 0.0.0-20260705182501-bb2a4e1f08c8. The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access.
2. How severe is CVE-2026-73293? CVE-2026-73293 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/semaphoreui/semaphore are affected by CVE-2026-73293? github.com/semaphoreui/semaphore (go) versions < 0.0.0-20260705182501-bb2a4e1f08c8 is affected.
4. Is there a fix for CVE-2026-73293? Yes. CVE-2026-73293 is fixed in 0.0.0-20260705182501-bb2a4e1f08c8. Upgrade to this version or later.
5. Is CVE-2026-73293 exploitable, and should I be worried? Whether CVE-2026-73293 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-73293 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-73293? Upgrade github.com/semaphoreui/semaphore to 0.0.0-20260705182501-bb2a4e1f08c8 or later.