gotify/server vulnerable to Cross-site Scripting in the application image file upload

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.6 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N

EPSS

• CVE-2022-46181: 0.55% estimated exploitation activity in the next 30 days; percentile 45.77 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact The XSS vulnerability allows authenticated users to upload .html files. With that, an attacker could execute client side scripts if another user opened a link, such as: An attacker could potentially take over the account of the user that clicked the link. Keep in mind, the Gotify UI won't natively expose such a malicious link, so an attacker has to get the user to open the malicious link in a context outside of Gotify. Patches The vulnerability has been fixed in version 2.2.2. Workarounds You can block access to non image files via a reverse proxy in the ./image directory. References https://github.com/gotify/server/pull/534 https://github.com/gotify/server/pull/535 --- Thanks to rickshang (aka 无在无不在) for discovering and reporting this bug.

Published by the source

30 Dec 2022, 00:58 UTC

Last modified by the source

29 Jan 2023, 05:05 UTC

Source last checked

26 Oct 2026, 14:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-xv6x-456v-24xh

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-46181

Advisory: gotify/server vulnerable to Cross-site Scripting in the application image file upload
IDs: CVE-2022-46181, GHSA-xv6x-456v-24xh
Record: https://patchnext.com/advisories/cve-2022-46181 (revision 1, source checked 26 Oct 2026, 14:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/gotify/server 2.2.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/gotify/server: affected <= 2.2.1; fixed in 2.2.2

## Suggested inspection (read-only)
- Go github.com/gotify/server: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/gotify/server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-xv6x-456v-24xh (GitHub-reviewed advisory GHSA-xv6x-456v-24xh lists affected ranges: Go github.com/gotify/server >=0 <=2.2.1)

Commands are suggestions: review each one before running it.