Description
Gotify server is a simple server for sending and receiving messages in real-time per WebSocket. Prior to 3.0.0, the password change endpoint (POST /current/user/password) accepts a valid client token without requiring the account's current password or another elevated authentication step. An attacker who obtains a client token can set a new password for the associated user, taking control of password authentication and forcing account recovery through an administrator or direct database access. This issue is fixed in version 3.0.0.
Published: 2026-10-13
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Remote Authentication Bypass and Account Takeover
Action: Apply Patch
AI Analysis

Impact

The Gotify server’s password change endpoint allows a client that holds any valid client token to change the associated user’s password without proving knowledge of the current password or any other higher‑level authentication step. This flaw, classified as CWE‑620, effectively lets an attacker take over the authenticated user’s account. Once the password is changed, the attacker can authenticate as that user or force a recovery‑by‑admin or database‑level process to regain control of the account, compromising confidentiality and integrity of account credentials.

Affected Systems

Gotify server versions prior to 3.0.0 are affected, specifically the POST /current/user/password endpoint in the server product from the Gotify vendor. The issue is resolved in version 3.0.0 and later.

Risk and Exploitability

The CVSS score of 5.3 indicates a medium severity vulnerability. No EPSS score is available, so the current exploitation probability cannot be quantified. The vulnerability is not listed in the CISA KEV catalog. The typical attack vector involves an attacker who has obtained or intercepted a client token—such as through legitimate client activity or a token‑leak scenario—making the exploit straightforward once a token is in hand. Without elevated privileges or additional authentication, the attacker can change the password and gain full control of the user’s account.

Generated by OpenCVE AI on October 13, 2026 at 17:39 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Gotify server to version 3.0.0 or later to apply the official fix.
  • Revoke or rotate all currently issued client tokens to invalidate any that may have been compromised before patching.
  • Verify that the password‑change endpoint now requires either the current password or additional elevated authentication before allowing a password change, and review access controls on related API endpoints.

Generated by OpenCVE AI on October 13, 2026 at 17:39 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-3hcj-9m7p-wwm9 Gotify: Insufficiently Protected Password Change endpoint
History

Wed, 14 Oct 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Tue, 13 Oct 2026 18:00:00 +0000

Type Values Removed Values Added
First Time appeared Gotify
Gotify server
Vendors & Products Gotify
Gotify server

Tue, 13 Oct 2026 14:30:00 +0000

Type Values Removed Values Added
Description Gotify server is a simple server for sending and receiving messages in real-time per WebSocket. Prior to 3.0.0, the password change endpoint (POST /current/user/password) accepts a valid client token without requiring the account's current password or another elevated authentication step. An attacker who obtains a client token can set a new password for the associated user, taking control of password authentication and forcing account recovery through an administrator or direct database access. This issue is fixed in version 3.0.0.
Title Gotify: Insufficiently Protected Password Change endpoint
Weaknesses CWE-620
References
Metrics cvssV4_0

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-10-14T14:45:36.133Z

Reserved: 2026-09-29T14:18:02.920Z

Link: CVE-2026-102603

cve-icon Vulnrichment

Updated: 2026-10-14T14:44:57.323Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-10-13T15:17:30.383

Modified: 2026-10-16T16:00:33.533

Link: CVE-2026-102603

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-13T17:45:17Z

Weaknesses
  • CWE-620

    Unverified Password Change