Medium · CVSS 5.3CVE-2026-102603

Gotify: Insufficiently Protected Password Change endpointCVE-2026-102603

Answer in brief

CVE-2026-102603 records a Medium severity (CVSS 5.3) vulnerability in Gotify: Insufficiently Protected Password Change endpoint. The current sources do not mark it as known exploited. The current feed maps gotify/server (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 13, 2026Updated Oct 13, 2026Source checked Oct 13, 2026First seen by HOL Oct 13, 2026Material review Oct 13, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 5.3
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 5.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps gotify/server (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
gotify/servergeneric	<3.0.0	3.0.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for gotify/server.
Review the reported fix. Update gotify/server to 3.0.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Oct 13, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 13, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 13, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.