Is CVE-2026-102603 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-102603 being exploited in the wild.

How severe is CVE-2026-102603?

Medium severity, with a CVSS score of 4, published 13 October 2026.

Which products and versions are affected?

github.com/gotify/server (Go) SEMVER:introduced=0; github.com/gotify/server/v2 (Go) <= 2.9.1, SEMVER:introduced=0, SEMVER:introduced=0,last_affected=2.9.1; github.com/gotify/server/v3 (Go) < 3.0.0, SEMVER:introduced=0,fixed=3.0.0; Gotify Server <= 2.9.1.

How is CVE-2026-102603 attacked?

It is attacked over the network.

Am I affected by CVE-2026-102603?

Check whether you run github.com/gotify/server (Go), github.com/gotify/server/v2 (Go), github.com/gotify/server/v3 (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-102603: Gotify password change endpoint missing verification

Q: Is there a fix for CVE-2026-102603?

Yes. github.com/gotify/server/v3 (Go): upgrade to 3.0.0 or later. Until then: Restrict network access to state-changing endpoints under /user and /current/user to trusted networks only, or upgrade to version 3.0.0 which requires step-up authentication (re-entering the account password) to change the password. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-102603 attacked?

It is attacked over the network.

Q: Am I affected by CVE-2026-102603?

Check whether you run github.com/gotify/server (Go), github.com/gotify/server/v2 (Go), github.com/gotify/server/v3 (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-102603 · Severity: medium · CVSS 4 · Published 2026-10-13

Gotify, a push notification server, has a vulnerability in its password change feature that allows attackers with a valid client token to change a user's password without knowing the current password. An attacker who obtains a client token can hijack accounts, forcing administrators to manually recover them or reset the database. This is a privilege escalation risk for multi-user deployments.

Technologies: github.com/gotify/server (Go), github.com/gotify/server/v2 (Go). Vendors: Go.

Quick answers

Is CVE-2026-102603 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-102603 being exploited in the wild.
How severe is CVE-2026-102603?: Medium severity, with a CVSS score of 4, published 13 October 2026.
Which products and versions are affected?: github.com/gotify/server (Go) SEMVER:introduced=0; github.com/gotify/server/v2 (Go) <= 2.9.1, SEMVER:introduced=0, SEMVER:introduced=0,last_affected=2.9.1; github.com/gotify/server/v3 (Go) < 3.0.0, SEMVER:introduced=0,fixed=3.0.0; Gotify Server <= 2.9.1.
Is there a fix for CVE-2026-102603?: Yes. github.com/gotify/server/v3 (Go): upgrade to 3.0.0 or later. Until then: Restrict network access to state-changing endpoints under /user and /current/user to trusted networks only, or upgrade to version 3.0.0 which requires step-up authentication (re-entering the account password) to change the password. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-102603 attacked?: It is attacked over the network.
Am I affected by CVE-2026-102603?: Check whether you run github.com/gotify/server (Go), github.com/gotify/server/v2 (Go), github.com/gotify/server/v3 (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/gotify/server/v3 (Go): upgrade to 3.0.0 or later
```
go get github.com/gotify/server/v3@v3.0.0
```

Restrict network access to state-changing endpoints under /user and /current/user to trusted networks only, or upgrade to version 3.0.0 which requires step-up authentication (re-entering the account password) to change the password.

Technical details

The POST /current/user/password endpoint in Gotify versions ≤ 2.9.1 does not require the current password to be provided during password changes, requiring only a valid client token (CWE-620: Unverified Password Change). An attacker with a stolen or leaked token can change the target user's password without additional authentication, causing account lockout and requiring admin intervention to recover access.

Affected products

Gotify server <= 2.9.1

Identifiers

CVE-2026-102603
GHSA-3hcj-9m7p-wwm9
GO-2026-6772

Timeline

2026-07-24: disclosed
2026-10-15: advisory
2026-10-15: patched: Patched in v3.0.0

References

https://api.github.com/users/scumfrog

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.