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

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-17 06:13 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

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.

Description quoted from the CVE record (assigned by GitHub_M, published 2026-08-12).

Weakness: CWE-352: Cross-Site Request Forgery (CSRF); CWE-620: Unverified Password Change

How it can be exploited

Exploitable over the network with low attack complexity needing no privileges and a user must take an action. Impact: confidentiality high, integrity high, availability low. CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L

CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: total.

Public exploit evidence (Exploit Observer)

Exploit Observer found 4 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 10 references on Exploit Observer

Live scores

EPSS
0.002
low predicted chance of attack
VEDAS
0.985
strong exploit evidence
On CISA KEV
Not listed
Detection rule
Suricata

Who is affected

ProductAffectedNot affected
Semaphoreui semaphoreversion < 2.18.21Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.

How to detect it

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-73292 Semaphore - Cross-Site Request Forgery Password Change. Add them to your Suricata rule set and reload.

Show the rules
suricata
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-73292 Semaphore - Cross-Site Request Forgery Password Change"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/api/users/"; fast_pattern; content:"/password"; distance:0; pcre:"/\/api\/users\/\d+\/password$/"; classtype:web-application-attack; reference:cve,CVE-2026-73292; reference:url,https://www.exploit.observer/?keyword=CVE-2026-73292&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=semaphore&match=exact; sid:1098802; rev:1;)

CVE-2026-73292.rules on GitHub

References

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.

Supporting partners