Vulnerability in github.com/gotify/server/v2 (CVE-2026-102603)
Summary
Vulnerability in github.com/gotify/server/v2 (CVE-2026-102603). Risk of unauthorized operations or information disclosure. Exploitable via POST /current/user/password. Mitigation: upgrade to 3.0.0 or later.
Original description
The description as published by the source.
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
/userand/current/userto trusted networks.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-102603 has been found in github.com/gotify/server/v2.
Attackers can target a specific entry point like POST /current/user/password over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/gotify/server/v2 to 3.0.0 or later.
If unsure, ask your IT team or search "github.com/gotify/server/v2 CVE-2026-102603" on the vendor's site.
CVE-2026-102603 (github.com/gotify/server/v2) — CWE-620
Attack surface: POST /current/user/password
Patched: 3.0.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-620) exists in github.com/gotify/server/v2. Attackers reach the vulnerable code path via POST /current/user/password.
Check the vendor advisory for the affected versions of github.com/gotify/server/v2. Attack surface: POST /current/user/password.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 3.0.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /current/user/password requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/gotify/server/v2' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/gotify/server/v2' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/gotify/server/v2を grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /current/user/password' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /current/user/passwordへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/gotify/server/v2 to 3.0.0ステージング環境で 3.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /current/user/password on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。