Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Nezha Monitoring (Go module github.com/nezhahq/nezha) versions from 1.4.0 up to but not including 1.14.15-0.20260517022419-d06d539d34c1 are affected. An authenticated user with the RoleMember role can send requests to user-supplied URLs through the notification endpoints, and the full response body from internal hosts is returned to them, enabling server-side request forgery. The source gives few details on the exact conditions beyond this. Upgrade to 1.14.15-0.20260517022419-d06d539d34c1 or later, which contains the fix.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.7 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0034, the 27th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:06 UTC First seen by agentprime
- 31 Oct 2026, 15:06 UTC Confirmed by OSV