Cyber Resilience

CVE-2026-73292

CSRF

Published
12 August 2026
Modified
12 August 2026
CVSS Score v3.1 8.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L
EPSS Score 0.0019 9th percentile
Risk Priority 59 floored blend · peak EPSS

Summary

CVE-2026-73292 is a high-severity CSRF (CWE-352) vulnerability. Its CVSS base score is 8.3 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Account Manipulation (T1098); ranked at the 9th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to IA-11 (Re-authentication) and IA-5 (Authenticator Management) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

administrator's or another user's password after user interaction. This issue is fixed in version 2.18.21.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1098 Account Manipulation Persistence
Adversaries may manipulate accounts to maintain and/or elevate access to victim systems.
T1098.001 Additional Cloud Credentials Persistence
Adversaries may add adversary-controlled credentials to a cloud account to maintain persistent access to victim accounts and instances within the environment.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-34077Shared CWE-620
CVE-2026-15964Shared CWE-620
CVE-2024-9431Shared CWE-620
CVE-2025-4558Shared CWE-620
CVE-2026-56305Shared CWE-620
CVE-2023-4465Shared CWE-620
CVE-2024-47784Shared CWE-620
CVE-2025-71328Shared CWE-620
CVE-2026-44733Shared CWE-620
CVE-2024-21757Shared CWE-620

Affected Assets

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V3.3.2
  • V3.5.1
  • V10.2.1

Mitigating Controls (NIST 800-53 r5) AI

Re-authentication explicitly requires users to prove identity before performing sensitive actions such as password changes.

Authenticator management requires identity verification during password distribution and changes, directly stopping unverified password updates.

Access enforcement requires verifying that state-changing requests originate from the authenticated user rather than a forged cross-site source.

Protecting session authenticity prevents attackers from replaying or forging authenticated requests via the victim's browser.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-01 mostly match
prevents

Credential management practices directly enforce re-authentication for password changes.

PR.AA-03 mostly match
prevents

Authentication requirements include verifying identity before allowing credential modifications.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require anti-CSRF controls such as tokens or SameSite attributes.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

degrades

Requires secure management of authentication information, directly addressing the need to verify the original password before allowing a change.

mitigates

By denying access to phishing or malicious sites, the control lowers the likelihood that a user will be tricked into submitting a forged request that performs an unintended action on another site.

prevents

Mandates secure authentication mechanisms, which include verifying existing credentials before permitting password changes.

none

Identity management processes can incorporate verification steps, but the control itself does not explicitly require password-change verification.

none

Contextual intelligence about emerging CSRF toolkits can be translated into updated anti-CSRF token or same-site policy configurations across applications.

none

Information access restriction can be strengthened by password verification, yet the control focuses on access rights rather than change procedures.

References