Is CVE-2026-53522 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-53522 being exploited in the wild.

How severe is CVE-2026-53522?

Medium severity, with a CVSS score of 6.5, published 12 June 2026.

Which products and versions are affected?

github.com/nezhahq/nezha (Go) >= 1.0.0, = 1.0.0, < 2.2.0; NezhaHQ Nezha Monitoring 1.0.0 to < 2.2.0.

Is there a fix for CVE-2026-53522?

Yes. github.com/nezhahq/nezha (Go): upgrade to 2.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-53522 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-53522?

Check whether you run github.com/nezhahq/nezha (Go), NezhaHQ Nezha or NezhaHQ Nezha Monitoring at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-53522: Nezha Monitoring resource exhaustion via unbounded WebSocket streams

Q: Is there a fix for CVE-2026-53522?

Yes. github.com/nezhahq/nezha (Go): upgrade to 2.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-53522 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-53522?

Check whether you run github.com/nezhahq/nezha (Go), NezhaHQ Nezha or NezhaHQ Nezha Monitoring at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-53522 · Severity: medium · CVSS 6.5 · Published 2026-06-12

Nezha Monitoring is a dashboard used to monitor and manage remote servers. A vulnerability in its terminal and file management features allows an authenticated user to open an unlimited number of connections. This can be used to crash the monitoring dashboard or the remote servers being monitored by exhausting their memory and processing power, leading to a complete loss of monitoring capabilities.

Technologies: github.com/nezhahq/nezha (Go), NezhaHQ Nezha. Vendors: Go, NezhaHQ.

Quick answers

Is CVE-2026-53522 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-53522 being exploited in the wild.
How severe is CVE-2026-53522?: Medium severity, with a CVSS score of 6.5, published 12 June 2026.
Which products and versions are affected?: github.com/nezhahq/nezha (Go) >= 1.0.0, < 2.2.0, SEMVER:introduced=1.0.0, SEMVER:introduced=1.0.0,fixed=2.2.0; NezhaHQ Nezha >= 1.0.0, < 2.2.0; NezhaHQ Nezha Monitoring 1.0.0 to < 2.2.0.
Is there a fix for CVE-2026-53522?: Yes. github.com/nezhahq/nezha (Go): upgrade to 2.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-53522 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-53522?: Check whether you run github.com/nezhahq/nezha (Go), NezhaHQ Nezha or NezhaHQ Nezha Monitoring at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/nezhahq/nezha (Go): upgrade to 2.2.0 or later
```
go get github.com/nezhahq/nezha@v2.2.0
```

Technical details

The Nezha dashboard contains a resource exhaustion vulnerability in the `createTerminal` and `createFM` endpoints. These endpoints call `CreateStreamWithPurpose`, which inserts new stream contexts into an unbounded Go map without per-user rate limiting or global connection caps. Each stream triggers the allocation of goroutines, channels, and 1MB I/O buffers on the dashboard, while also spawning PTY/shell processes on the monitored agents via gRPC. An authenticated attacker with standard server execution or file management permissions can programmatically open thousands of streams to exhaust dashboard memory and agent resources. The issue is fixed in version 2.2.0 by implementing concurrency controls and stream limits.

Affected products

nezhahq nezha >= 1.0.0, < 2.2.0

Identifiers

CVE-2026-53522
GHSA-jg62-j5h6-8mpq
GO-2026-5831

Timeline

2026-06-05: disclosed: Initial publication by nezhahq
2026-06-12: advisory: NVD publication
2026-06-26: patched: GitHub Advisory Database entry updated with patch information

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.