Is CVE-2026-73292 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-73292 being exploited in the wild.

How severe is CVE-2026-73292?

High severity, with a CVSS score of 8.3, published 12 August 2026.

Which products and versions are affected?

github.com/semaphoreui/semaphore (Go) < 0.0.0-20260707190631-c59c3dc9035b, SEMVER:introduced=0,fixed=0.0.0-20260707190631-c59c3dc9035b; SemaphoreUI Semaphore < 0.0.0-20260707190631-c59c3dc9035b, including 2.18.20.

Is there a fix for CVE-2026-73292?

Yes. github.com/semaphoreui/semaphore (Go): upgrade to 0.0.0-20260707190631-c59c3dc9035b or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-73292 attacked?

It is attacked from the adjacent network, in a web application.

Am I affected by CVE-2026-73292?

Check whether you run github.com/semaphoreui/semaphore (Go) or SemaphoreUI Semaphore at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-73292: Semaphore UI CSRF in password change endpoint

Q: Is there a fix for CVE-2026-73292?

Yes. github.com/semaphoreui/semaphore (Go): upgrade to 0.0.0-20260707190631-c59c3dc9035b or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-73292 attacked?

It is attacked from the adjacent network, in a web application.

Q: Am I affected by CVE-2026-73292?

Check whether you run github.com/semaphoreui/semaphore (Go) or SemaphoreUI Semaphore at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-73292 · Severity: high · CVSS 8.3 · Published 2026-08-12

Semaphore UI is an orchestration and workflow automation platform. This vulnerability allows an attacker to silently change any user's password—including administrators—by tricking them into visiting a malicious website while logged into Semaphore. With no additional security checks required, an attacker can gain full administrative control of the entire Semaphore instance, leading to potential data theft, system compromise, and operational disruption.

Technologies: github.com/semaphoreui/semaphore (Go), SemaphoreUI Semaphore. Vendors: Go, SemaphoreUI.

Quick answers

Is CVE-2026-73292 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-73292 being exploited in the wild.
How severe is CVE-2026-73292?: High severity, with a CVSS score of 8.3, published 12 August 2026.
Which products and versions are affected?: github.com/semaphoreui/semaphore (Go) < 0.0.0-20260707190631-c59c3dc9035b, SEMVER:introduced=0,fixed=0.0.0-20260707190631-c59c3dc9035b; SemaphoreUI Semaphore < 0.0.0-20260707190631-c59c3dc9035b, including 2.18.20.
Is there a fix for CVE-2026-73292?: Yes. github.com/semaphoreui/semaphore (Go): upgrade to 0.0.0-20260707190631-c59c3dc9035b or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-73292 attacked?: It is attacked from the adjacent network, in a web application.
Am I affected by CVE-2026-73292?: Check whether you run github.com/semaphoreui/semaphore (Go) or SemaphoreUI Semaphore at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/semaphoreui/semaphore (Go): upgrade to 0.0.0-20260707190631-c59c3dc9035b or later
```
go get github.com/semaphoreui/semaphore@v0.0.0-20260707190631-c59c3dc9035b
```

Technical details

This is a classic Cross-Site Request Forgery (CSRF) vulnerability combined with unverified password change (CWE-352, CWE-620). The /api/users/{id}/password endpoint fails to implement CSRF protection—no anti-CSRF token is validated, no current password confirmation is required, and the session cookie lacks SameSite attribute enforcement. An attacker can craft a malicious web page containing a hidden form that automatically submits a POST request to change the password when visited by an authenticated user. The attack requires only that the victim be logged into Semaphore in the same browser and visit the attacker-controlled page; no user interaction beyond clicking a link is needed. A working proof-of-concept demonstrates silent password changes via form submission with text/plain encoding to bypass same-origin policy restrictions. The vulnerability is exploitable remotely and affects all versions prior to commit c59c3dc9035b.

Affected products

semaphoreui semaphore < 0.0.0-20260707190631-c59c3dc9035b, including 2.18.20

Identifiers

CVE-2026-73292
GHSA-8cj9-r88m-8945
GO-2026-6370

Timeline

2026-09-03: disclosed: Vulnerability disclosed via GitHub Advisory GHSA-8cj9-r88m-8945 and CVE-2026-73292
2026-07-07: patched: Fixed in commit c59c3dc9035b, released in v2.18.21
2026-08-12: advisory: Published to National Vulnerability Database

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.