github.com/nezhahq/nezha vulnerabilities
- Registry
- Go
- Latest
- 1.14.14
33 known advisories
The latest version, 1.14.14, is affected by 27 of them.
Is your project on an affected github.com/nezhahq/nezha?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for github.com/nezhahq/nezha
Nezha Monitoring: Whole-instance DoS in Nezha dashboard: a member can crash the process for every tenant in github.com/nezhahq/nezha
- Affected
- >=0.0.0-20260628010923-fd31e5f1b0f8 <0.0.0-20260721131105-c893aa57867d
- Fixed in
- 0.0.0-20260721131105-c893aa57867d
Nezha Monitoring: Whole-instance DoS in Nezha dashboard: a member can crash the process for every tenant
- Affected
- >=0.0.0-20260628010923-fd31e5f1b0f8 <0.0.0-20260721131105-c893aa57867d
- Fixed in
- 0.0.0-20260721131105-c893aa57867d
Nezha: OAuth2 redirect_uri Host header injection regression when dashboard_host is empty in github.com/nezhahq/nezha
- Affected
- All versions
- Fixed in
- No fix released
Nezha: OAuth2 redirect_uri Host header injection regression when dashboard_host is empty
- Affected
- 2.2.3
- Fixed in
- No fix released
Nezha's authenticated agents can forge service-monitor results for other users' services in github.com/nezhahq/nezha
- Affected
- >=1.0.0 <1.14.15-0.20260521020202-02129f16fb15
- Fixed in
- 1.14.15-0.20260521020202-02129f16fb15
Nezha vulnerable to cross-tenant terminal/file-manager session hijack via WebSocket stream UUID without ownership check in github.com/nezhahq/nezha
- Affected
- All versions · >=1.14.13
- Fixed in
- No fix released
Nezha Monitoring: Authenticated users can claim the dashboard Host through NAT and preempt all dashboard routing in github.com/nezhahq/nezha
- Affected
- All versions
- Fixed in
- No fix released
Nezha Monitoring: Stored future DDNS profile ID allows unauthorized use of another user's DDNS profile context in github.com/nezhahq/nezha
- Affected
- All versions
- Fixed in
- No fix released
Nezha Monitoring: Pre-auth path traversal via /dashboard.. prefix confusion leaks jwt_secret_key in github.com/nezhahq/nezha
- Affected
- All versions
- Fixed in
- No fix released
Nezha Monitoring: OAuth2 Redirect URL — Host Header Injection in github.com/nezhahq/nezha
- Affected
- >=1.0.0
- Fixed in
- No fix released
Nezha Monitoring: Unbounded WebSocket Streams — Resource Exhaustion DoS in github.com/nezhahq/nezha
- Affected
- >=1.0.0
- Fixed in
- No fix released
Nezha Dashboard: DDNS and Notification credential exposure via unredacted list API in github.com/nezhahq/nezha
- Affected
- All versions
- Fixed in
- No fix released
Nezha Dashboard: DDNS and Notification credential exposure via unredacted list API
- Affected
- <2.2.5
- Fixed in
- 2.2.5
Nezha Monitoring: OAuth2 Redirect URL — Host Header Injection
- Affected
- >=1.0.0 <2.2.0
- Fixed in
- 2.2.0
Nezha Monitoring: Unbounded WebSocket Streams — Resource Exhaustion DoS
- Affected
- >=1.0.0 <2.2.0
- Fixed in
- 2.2.0
Nezha Monitoring: Pre-auth path traversal via /dashboard.. prefix confusion leaks jwt_secret_key
- Affected
- <2.0.13
- Fixed in
- 2.0.13
Nezha Monitoring: Stored future DDNS profile ID allows unauthorized use of another user's DDNS profile context
- Affected
- >=2.0.14 <2.1.0
- Fixed in
- 2.1.0
Nezha Monitoring: Authenticated users can claim the dashboard Host through NAT and preempt all dashboard routing
- Affected
- >=2.0.14 <2.1.0
- Fixed in
- 2.1.0
Nezha vulnerable to cross-tenant terminal/file-manager session hijack via WebSocket stream UUID without ownership check
- Affected
- >=1.14.13 <=1.14.14 · >=2.0.0 <2.0.10
- Fixed in
- 2.0.10
Nezha Monitoring: RoleMember can fire other users' cron tasks via AlertRule.FailTriggerTasks (no ownership check) in github.com/nezhahq/nezha
- Affected
- >=1.4.0 <1.14.15-0.20260517022419-d7526351cf97
- Fixed in
- 1.14.15-0.20260517022419-d7526351cf97
Nezha's private services (`EnableShowInService: false`) are enumerable via per-server endpoints, leaking name and timing data in github.com/nezhahq/nezha
- Affected
- All versions
- Fixed in
- No fix released
Nezha Monitoring: RoleMember-reachable SSRF with full response-body reflection via POST /api/v1/notification in github.com/nezhahq/nezha
- Affected
- >=1.4.0 <1.14.15-0.20260517022419-d06d539d34c1
- Fixed in
- 1.14.15-0.20260517022419-d06d539d34c1
Nezha Monitoring: Nezha WebSocket server stream discloses cross-tenant server telemetry to authenticated members in github.com/nezhahq/nezha
- Affected
- >=1.4.0 <1.14.15-0.20260517034128-05e5da253519
- Fixed in
- 1.14.15-0.20260517034128-05e5da253519
Nezha has cross-site GET request that can trigger stored cron commands on a victim's agents in github.com/nezhahq/nezha
- Affected
- >=1.0.0
- Fixed in
- No fix released
Nezha Monitoring: RoleMember can run shell on every server (cross-tenant RCE) via POST /api/v1/cron in github.com/nezhahq/nezha
- Affected
- >=1.4.0 <1.14.15-0.20260517022419-d7526351cf97
- Fixed in
- 1.14.15-0.20260517022419-d7526351cf97
Nezha's private services (`EnableShowInService: false`) are enumerable via per-server endpoints, leaking name and timing data
- Affected
- >=2.0.0 <2.0.14
- Fixed in
- 2.0.14
Nezha has cross-site GET request that can trigger stored cron commands on a victim's agents
- Affected
- >=1.0.0 <2.0.14
- Fixed in
- 2.0.14
Nezha's authenticated agents can forge service-monitor results for other users' services
- Affected
- >=0.20.0 <1.14.15-0.20260521020202-02129f16fb15 · >=2.0.0 <2.0.12
- Fixed in
- 1.14.15-0.20260521020202-02129f16fb15, 2.0.12
Nezha's authenticated DDNS webhook configuration allows blind SSRF from the dashboard host
- Affected
- >=0.20.0 <2.0.10
- Fixed in
- 2.0.10
Nezha Monitoring: Nezha WebSocket server stream discloses cross-tenant server telemetry to authenticated members
- Affected
- >=1.4.0 <1.14.15-0.20260517034128-05e5da253519
- Fixed in
- 1.14.15-0.20260517034128-05e5da253519
Nezha Monitoring: RoleMember can run shell on every server (cross-tenant RCE) via POST /api/v1/cron
- Affected
- >=1.4.0 <1.14.15-0.20260517022419-d7526351cf97
- Fixed in
- 1.14.15-0.20260517022419-d7526351cf97
Nezha Monitoring: RoleMember can fire other users' cron tasks via AlertRule.FailTriggerTasks (no ownership check)
- Affected
- >=1.4.0 <1.14.15-0.20260517022419-d7526351cf97
- Fixed in
- 1.14.15-0.20260517022419-d7526351cf97
Nezha Monitoring: RoleMember-reachable SSRF with full response-body reflection via POST /api/v1/notification
- Affected
- >=1.4.0 <1.14.15-0.20260517022419-d06d539d34c1
- Fixed in
- 1.14.15-0.20260517022419-d06d539d34c1
Is your github.com/nezhahq/nezha version vulnerable?
- github.com/nezhahq/nezha 1.1427 advisories in 1.14.14
- github.com/nezhahq/nezha 1.1326 advisories in 1.13.2
- github.com/nezhahq/nezha 1.1226 advisories in 1.12.4
- github.com/nezhahq/nezha 1.1126 advisories in 1.11.0
- github.com/nezhahq/nezha 1.1026 advisories in 1.10.8
- github.com/nezhahq/nezha 1.926 advisories in 1.9.11
- github.com/nezhahq/nezha 0.2011 advisories in 0.20.13
- github.com/nezhahq/nezha 0.199 advisories in 0.19.20
- github.com/nezhahq/nezha 0.189 advisories in 0.18.14
- github.com/nezhahq/nezha 0.179 advisories in 0.17.10
- github.com/nezhahq/nezha 0.169 advisories in 0.16.29
- github.com/nezhahq/nezha 0.159 advisories in 0.15.20
Which of your client projects still run an old github.com/nezhahq/nezha?
NPMscan reads the go.mod in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Go packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Go registry.