Skip to content
Fencer Vulns
high 8.3

CVE-2026-73292 json

Semaphore UI: CSRF vulnerability on password change endpoint - No CSRF token or password confirmation

published 2026-08-12 2 mo ago modified 2026-10-24 15 d ago also GHSA-8cj9-r88m-8945 , GO-2026-6370 , EUVD-2026-57311

cvss
8.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 14%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/semaphoreui/semaphore 0.0.0-20260707190631-c59c3dc9035b
  • govulncheck-vulndb SLES 16.0, SLES for SAP applications 16.0 0.0.20260916T180043-160000.1.1

suse advisories SUSE-SU-2026:23855-1SUSE-SU-2026:23863-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260916T180043-160000.1.1

opensuse advisories openSUSE-SU-2026:21897-1

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2 mo ago

Exploit prediction

0.23% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 8.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L
GitHub 3.1 7.6 CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L

Affected packages

ecosystem package affected fixed in
go github.com/semaphoreui/semaphore
<0.0.0-20260707190631-c59c3dc9035b
0.0.0-20260707190631-c59c3dc9035b

Affected products

  • semaphoreui semaphore

Classification

Weakness
  • CWE-352 Cross-Site Request Forgery
  • CWE-620 Unverified Password Change

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.