What is CVE-2026-102603?

CVE-2026-102603 is a medium-severity security vulnerability in github.com/gotify/server/v2 (go), affecting versions <= 2.9.1. It is fixed in 3.0.0.

Which packages are affected by CVE-2026-102603?

github.com/gotify/server/v2 (go) versions <= 2.9.1; github.com/gotify/server/v3 (go) versions < 3.0.0.

Is there a fix for CVE-2026-102603?

Yes. CVE-2026-102603 is fixed in 3.0.0. Upgrade to this version or later.

Is CVE-2026-102603 exploitable, and should I be worried?

Whether CVE-2026-102603 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-102603 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-102603 in github.com/gotify/server/v2

Q: Which packages are affected by CVE-2026-102603?

github.com/gotify/server/v2 (go) versions <= 2.9.1; github.com/gotify/server/v3 (go) versions < 3.0.0.

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

Yes. CVE-2026-102603 is fixed in 3.0.0. Upgrade to this version or later.

Q: Is CVE-2026-102603 exploitable, and should I be worried?

Whether CVE-2026-102603 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-102603 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-102603?

Upgrade github.com/gotify/server/v3 to 3.0.0 or later.

Summary

Gotify: Insufficiently Protected Password Change endpoint

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.

Impact

Affected versions

github.com/gotify/server/v2 (<= 2.9.1) github.com/gotify/server/v3 (< 3.0.0)

Security releases

github.com/gotify/server/v3 → 3.0.0 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade github.com/gotify/server/v3 to 3.0.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-102603? CVE-2026-102603 is a medium-severity security vulnerability in github.com/gotify/server/v2 (go), affecting versions <= 2.9.1. It is fixed in 3.0.0.
Which packages are affected by CVE-2026-102603?
- github.com/gotify/server/v2 (go) (versions <= 2.9.1)
- github.com/gotify/server/v3 (go) (versions < 3.0.0)
Is there a fix for CVE-2026-102603? Yes. CVE-2026-102603 is fixed in 3.0.0. Upgrade to this version or later.
Is CVE-2026-102603 exploitable, and should I be worried? Whether CVE-2026-102603 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-102603 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-102603? Upgrade github.com/gotify/server/v3 to 3.0.0 or later.