Nezha Monitoring: RoleMember-reachable SSRF with full response-body reflection via POST /api/v1/notification

Exploitation

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

CVSS

8.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N

EPSS

• CVE-2026-46717: 0.34% estimated exploitation activity in the next 30 days; percentile 27.00 (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.

Summary nezha's dashboard supports two user roles: RoleAdmin (Role==0) and RoleMember (Role==1). The notification routes POST /api/v1/notification and PATCH /api/v1/notification/:id are wired through commonHandler rather than adminHandler — so a RoleMember user can call them. These handlers synchronously Send() an HTTP request to a user-controlled URL and reflect the entire response body (no size limit) back to the caller on any non-2xx response. Net effect: a low-privilege RoleMember can read intranet HTTP response bodies via the dashboard's hub. Affected versions Commit 50dc8e660326b9f22990898142c58b7a5312b42a and earlier on master. Reachability chain For comparison, /user routes ARE gated by adminHandler: adminHandler (controller.go:220-236) explicitly enforces user.Role.IsAdmin(). commonHandler (controller.go:214-218) does not. The vulnerable handler Identical pattern in updateNotification (PATCH /notification/:id) at lines 97-146. The reflection sink The full body (no size…

Published by the source

23 May 2026, 00:08 UTC

Last modified by the source

26 Jun 2026, 21:28 UTC

Source last checked

26 Oct 2026, 15:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-w4g9-mxgg-j532

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

# Patch Next advisory brief: CVE-2026-46717

Advisory: Nezha Monitoring: RoleMember-reachable SSRF with full response-body reflection via POST /api/v1/notification
IDs: CVE-2026-46717, GHSA-w4g9-mxgg-j532
Record: https://patchnext.com/advisories/cve-2026-46717 (revision 1, source checked 26 Oct 2026, 15:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/nezhahq/nezha 1.14.15-0.20260517022419-d06d539d34c1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/nezhahq/nezha: affected >= 1.4.0, < 1.14.15-0.20260517022419-d06d539d34c1; fixed in 1.14.15-0.20260517022419-d06d539d34c1

## Suggested inspection (read-only)
- Go github.com/nezhahq/nezha: 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/nezhahq/nezha.
- 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-w4g9-mxgg-j532 (GitHub-reviewed advisory GHSA-w4g9-mxgg-j532 lists affected ranges: Go github.com/nezhahq/nezha >=1.4.0 <1.14.15-0.20260517022419-d06d539d34c1)

Commands are suggestions: review each one before running it.