Advisory record · GHSA-8cj9-r88m-8945

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

CVSS 8.3 HighEPSS 0.0023 · 14th percentile

Published by the GitHub Advisory Database at 3 Sept 2026, 19:23 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/semaphoreui/semaphoreGo<0.0.0-20260707190631-c59c3dc9035b0.0.0-20260707190631-c59c3dc9035b
Identifiers
GHSA-8cj9-r88m-8945 · CVE-2026-73292 · GO-2026-6370
Weakness (CWE)
CWE-352 · CWE-620
Published
3 Sept 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Semaphore UI (Go module github.com/semaphoreui/semaphore) is vulnerable to cross-site request forgery on its password change endpoint, affecting versions before 0.0.0-20260707190631-c59c3dc9035b. An attacker can host a malicious page that silently submits a password change for a user who is logged in, including an administrator, and then take over that account. The source reports the issue was tested on version 2.18.20. Upgrade to 0.0.0-20260707190631-c59c3dc9035b or later.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.3 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0023, the 14th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:13 UTC First seen by agentprime
  2. 31 Oct 2026, 14:13 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.