GHSA-hvv7-hfrh-7gxj
MEDIUMGHSA-hvv7-hfrh-7gxj is a medium-severity (CVSS 6.5) Information Exposure vulnerability in github.com/nezhahq/nezha. O3 Security confirms whether GHSA-hvv7-hfrh-7gxj is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Nezha Monitoring: Nezha WebSocket server stream discloses cross-tenant server telemetry to authenticated members
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-hvv7-hfrh-7gxj plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 362,881 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/nezhahq/nezhaReal-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
Summary
Any authenticated non-admin member can connect to the server-status WebSocket and receive telemetry for all servers, including servers owned by other users. The normal server list API filters objects by HasPermission, but the WebSocket stream treats the presence of any authenticated user as authorization for the full unfiltered server list.
Details
The server WebSocket route is registered under the optional-auth group in cmd/dashboard/controller/controller.go:71-73:
optionalAuth := api.Group("", optionalAuthMw)
optionalAuth.GET("/ws/server", commonHandler(serverStream))
serverStream treats any CtxKeyAuthorizedUser as a member, without checking admin role or per-server ownership, in cmd/dashboard/controller/ws.go:123-139:
u, isMember := c.Get(model.CtxKeyAuthorizedUser)
var userId uint64
if isMember {
userId = u.(*model.User).ID
}
...
stat, err := getServerStat(count == 0, isMember)
The authorization boolean is then used as a full/guest switch in getServerStat in cmd/dashboard/controller/ws.go:160-184:
if authorized {
serverList = singleton.ServerShared.GetSortedList()
} else {
serverList = singleton.ServerShared.GetSortedListForGuest()
}
...
servers = append(servers, model.StreamServer{
ID: server.ID,
Name: server.Name,
PublicNote: utils.IfOr(withPublicNote, server.PublicNote, ""),
DisplayIndex: server.DisplayIndex,
Host: utils.IfOr(authorized, server.Host, server.Host.Filter()),
State: server.State,
CountryCode: countryCode,
LastActive: server.LastActive,
})
For authenticated members, GetSortedList() returns all servers and server.Host is not filtered. There is no call to server.HasPermission(c).
The streamed response model in model/server_api.go:5-20 includes server ID/name, public note, host details, runtime state, country code, last active time, and global online count. Host and state fields include platform version, agent version, CPU/GPU names, memory/disk/swap totals, architecture, virtualization, boot time, CPU load, memory/disk/swap usage, network transfer/speed, uptime, TCP/UDP/process counts, temperatures, and GPU utilization, as defined in model/host.go:20-38 and model/host.go:100-112.
The normal list endpoint has the expected object-level authorization. GET /api/v1/server is registered with listHandler in cmd/dashboard/controller/controller.go:113, and listHandler filters each returned object with HasPermission in cmd/dashboard/controller/controller.go:263-291:
filtered := filter(c, data)
...
return slices.DeleteFunc(s, func(e E) bool {
return !e.HasPermission(ctx)
})
The shared permission model in model/common.go:44-56 allows admins to see all objects but restricts members to objects whose UserID matches their user ID:
if user.Role == RoleAdmin {
return true
}
return user.ID == c.UserID
Mitigations checked:
- Guests receive
GetSortedListForGuest()andHost.Filter()output, but authenticated members bypass both guest restrictions. HideForGuestonly affects unauthenticated guests, not members.- The normal
/api/v1/serverlist endpoint useslistHandlerand is not affected in the same way. - No owner/admin filter is applied in the WebSocket path.
Candidate score: 12/14
- Reachability: 2, default WebSocket API
- Attacker control: 1, attacker controls authentication state and connection
- Privilege required: 1, authenticated member
- Sink impact: 2, cross-tenant sensitive telemetry disclosure
- Mitigation weakness: 2, no object-level auth in the WebSocket path
- Default exposure: 2, endpoint is part of default dashboard
- Safe PoC feasibility: 2, can be verified with local users/servers or statically
Exploitability gate: statically confirmed
- Reachable source:
GET /api/v1/ws/server - Default/common configuration: dashboard API exposed by default
- Missing/bypassed mitigation: member-vs-guest check replaces object-level authorization
- Impact-bearing sink: WebSocket response includes unfiltered all-server telemetry
- Safe proof: static source-to-sink proof; full runtime test blocked locally by unavailable Go 1.26 toolchain
- Affected version evidence: confirmed at commit
85b0dd2992733037b019442caffc6c049ba937dd(v2.0.7-1-g85b0dd2) - Variant review: normal server list endpoint and guest filtering were checked
PoC
Static local PoC steps:
- Start Nezha with two non-admin users and at least one server assigned to each user.
- Authenticate as user A.
- Connect to the WebSocket endpoint with user A's token, for example:
GET /api/v1/ws/server HTTP/1.1
Host: 127.0.0.1:8008
Cookie: nz-jwt=<user-a-token>
Upgrade: websocket
Connection: Upgrade
- Observe that the JSON messages contain entries for all servers from
singleton.ServerShared.GetSortedList(), including servers whoseUserIDdoes not match user A. - Compare with
GET /api/v1/serverusing the same token; that route is filtered throughlistHandler/HasPermissionand should only return user A's own servers.
Cleanup: no persistent state is created by the WebSocket connection.
Local dynamic confirmation note: the full project test/runtime could not be executed in this audit environment because the repository requires Go 1.26 and the local toolchain reported go: download go1.26 for linux/amd64: toolchain not available.
Impact
This is an authenticated horizontal information disclosure. A low-privileged member can continuously monitor other users' server inventory and live telemetry, including host platform details, agent versions, CPU/GPU details, resource usage, traffic counters, country code, and last-active timestamps. This may expose infrastructure composition, usage patterns, and operational state across tenants.
Suggested remediation
Apply object-level authorization in getServerStat for authenticated non-admin users. For each server in the stream, include it only if the current user is admin or server.UserID matches the authenticated user. Keep guest filtering and host redaction for unauthenticated users.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/nezhahq/nezha | ≥ 1.4.0&&< 1.14.15-0.20260517034128-05e5da253519 | 1.14.15-0.20260517034128-05e5da253519 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/nezhahq/nezha. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/nezhahq/nezha to 1.14.15-0.20260517034128-05e5da253519 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hvv7-hfrh-7gxj is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-hvv7-hfrh-7gxj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-hvv7-hfrh-7gxj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-hvv7-hfrh-7gxj in your dependencies?
O3 detects GHSA-hvv7-hfrh-7gxj across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.