CVE-2026-73292
Received Received - Intake

CSRF in Semaphore UI Password Change

Vulnerability report for CVE-2026-73292, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-12

Last updated on: 2026-08-12

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-12
Last Modified
2026-08-12
Generated
2026-09-01
AI Q&A
2026-08-12
EPSS Evaluated
2026-08-31
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
semaphoreui semaphore to 2.18.21 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-352 The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
CWE-620 When setting a new password for a user, the product does not require knowledge of the original password, or using another form of authentication.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a Cross-Site Request Forgery (CSRF) flaw in Semaphore UI versions 2.18.20 and earlier. It allows an unauthenticated attacker to change a user's password, including administrator accounts, by tricking an authenticated user into visiting a malicious website. The endpoint lacks CSRF protection and does not require password confirmation.

Detection Guidance

To detect this vulnerability, check if your Semaphore UI instance is running a version prior to 2.18.21. Use commands like 'curl -s https://your-semaphore-url | grep -i semaphore' or inspect the version in the web interface footer. Monitor network traffic for unauthorized password change requests to /api/users/{id}/password endpoints.

Impact Analysis

An attacker could take over user accounts, including administrator accounts, leading to unauthorized access to sensitive data and systems. The attacker needs to trick a logged-in user into visiting a malicious site, which then silently submits a password change request to the Semaphore instance.

Compliance Impact

This vulnerability could lead to unauthorized access to personal or sensitive data, violating GDPR and HIPAA requirements for data protection and access control. Organizations using affected versions may face compliance violations and potential legal consequences.

Mitigation Strategies

Immediately upgrade Semaphore UI to version 2.18.21 or later. Ensure HTTPS is enforced and session cookies have Secure and SameSite=Lax attributes. Review user accounts for unauthorized password changes and revoke suspicious sessions.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-73292. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart