CVE-2026-73292 Semaphore UI: CSRF vulnerability on password change endpoint - No CSRF token or password confirmation
An attacker can change an administrator's password via CSRF, leading to account takeover, requiring user interaction.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-73292?
CVE-2026-73292 is a high-severity vulnerability in semaphoreui semaphore, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
Semaphore UI is a web interface for managing DevOps tools. Prior to 2.18.21, the /api/users/{id}/password endpoint accepts a cross-site request using the authenticated user's semaphore session cookie without CSRF protection or current-password confirmation, allowing an unauthenticated attacker to change an administrator's or another user's password after user interaction. This issue is fixed in version 2.18.21.
Which versions are affected by CVE-2026-73292?
3 open source packages ship an affected version, including github.com/semaphoreui/semaphore.
| Package | Affected | Fixed in |
|---|---|---|
github.com/semaphoreui/semaphore Go | All versions | 0.0.0-20260707190631-c59c3dc9035b |
github.com/semaphoreui/semaphore Go | All versions | 0.0.0-20260707190631-c59c3dc9035b |
github.com/semaphoreui/semaphore Go | All versions | 0.0.0-20260707190631-c59c3dc9035b |
How do I fix CVE-2026-73292?
Upgrade github.com/semaphoreui/semaphore to 0.0.0-20260707190631-c59c3dc9035b or later.
Is CVE-2026-73292 being exploited?
There is no known exploitation of CVE-2026-73292 in the wild and no public exploit code.
Public exploit code: 1 proofs of concept on GitHub.
Sources
Also known as GHSA-8cj9-r88m-8945, GO-2026-6370.