Vulnerabilities

Vulnerability · CVE-2026-102603

Gotify: Insufficiently Protected Password Change endpoint

Published Oct 13, 2026 · catalog updated Oct 15, 2026 · Gotify: Insufficiently Protected Password

Check if you run it

No confirmed exploitation is on record for CVE-2026-102603. EPSS is 0.34%. Act only if a listed version of Gotify: Insufficiently Protected Password is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Gotify: Insufficiently Protected Password).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium5.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.34%
Remediation
Version ranges on file
Affected products
go github.com/gotify/server/v2 · go github.com/gotify/server/v3 · golang github.com · vendor gotify server

The password change endpoint ( ) in Gotify versions <= 2.9.1 does not require knowledge of the current password. An attacker in possession of a valid client token can set a new password for the affected user. Recovering the account requires administrator intervention or direct database access. ## PoC ## Mitigation - Upgrade to Gotify 3.0.0, which introduces step-up authentication: changing the password now requires re-authenticating with the account password, or - Restrict access to the state-changing endpoints under and to trusted networks.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • go github.com/gotify/server/v2<= 2.9.1
  • go github.com/gotify/server/v3< 3.0.0
  • golang github.comversion unspecified
  • vendor gotify serverversion unspecified

How to fix CVE-2026-102603

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-102603. EPSS is 0.34%. Act only if a listed version of Gotify: Insufficiently Protected Password is installed.

Which versions are affected?

Compare what you have installed with <= 2.9.1, < 3.0.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-620. EPSS 0.34%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 13, 2026 · CIRCL Vulnerability Lookup

    Detected

    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 passw

  2. Oct 14, 2026 · CIRCL Vulnerability Lookup

    Updated

    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 passw

  3. Oct 14, 2026 · NIST NVD

    Updated

    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 passw

  4. Oct 15, 2026 · GitHub Advisory Database

    Updated

    The password change endpoint ( ) in Gotify versions <= 2.9.1 does not require knowledge of the current password. An attacker in possession of a valid client token can set a new password for the affected user. Recovering the account requires administrator intervention or direct database access. ## PoC ## Mitigation - Upgrade to Gotify 3.0.0, which introduces step-up authentication: changing the pas

Sources

  • CIRCL Vulnerability LookupVulnerability recordCVE-2026-102603

    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 authenticat

    vulnerability.circl.lu
  • CVE.orgVulnerability recordCVE-2026-102603

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-102603

    30-day exploitation probability 0.3%

    first.org
  • GitHub Advisory DatabasePackage advisoryGHSA-3hcj-9m7p-wwm9

    Gotify: Insufficiently Protected Password Change endpoint

    github.com
  • GitLab Advisory DatabasePackage advisoryCVE-2026-102603

    The password change endpoint (POST /current/user/password) in Gotify versions <= 2.9.1 does not require knowledge of the current password. An attacker in possession of a valid client token can set a new password for the affected user. Recovering the account requires administrator intervention or direct database access.

    advisories.gitlab.com
  • NIST NVDVulnerability recordCVE-2026-102603

    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 authenticat

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.