CVE-2026-53522: CWE-770: Allocation of Resources Without Limits or Throttling in nezhahq nezha
Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&M tool. From version 1.0.0 to before version 2.2.0, the Nezha dashboard exposes two endpoints that create long-lived WebSocket streams to monitored agents: POST /api/v1/terminal → createTerminal() (terminal.go:27-67) and POST /api/v1/file → createFM() (fm.go:28-67). Both call rpc.NezhaHandlerSingleton.CreateStream(streamId, ...) which inserts a new ioStreamContext into an unbounded map[string]*ioStreamContext (s.ioStreams in io_stream.go:59-67). There is no per-user rate limit, no global semaphore, and no per-server connection cap. This issue has been patched in version 2.2.0.
AI Analysis
Technical Summary
Nezha Monitoring, a self-hosted monitoring tool, has a vulnerability (CVE-2026-53522) in versions before 2.2.0 where the endpoints POST /api/v1/terminal and POST /api/v1/file create long-lived WebSocket streams without any per-user rate limiting, global semaphore, or per-server connection caps. These streams are stored in an unbounded map, allowing potential resource exhaustion due to uncontrolled allocation of ioStreamContext objects. This vulnerability corresponds to CWE-770 (Allocation of Resources Without Limits or Throttling). The issue was patched in version 2.2.0.
Potential Impact
The vulnerability allows an attacker with at least low privileges to create unlimited long-lived WebSocket streams, potentially exhausting server resources and causing denial of service. There is no impact on confidentiality or integrity reported. The CVSS 3.1 base score is 6.5 (medium severity), reflecting network attack vector, low attack complexity, low privileges required, no user interaction, unchanged scope, no confidentiality or integrity impact, and high availability impact.
Mitigation Recommendations
Upgrade Nezha Monitoring to version 2.2.0 or later, where this vulnerability has been patched. There is no official vendor advisory provided here, and no temporary mitigations are described. Patch status is not explicitly confirmed but the description states the issue is fixed in 2.2.0, so upgrading is recommended.
CVE-2026-53522: CWE-770: Allocation of Resources Without Limits or Throttling in nezhahq nezha
Description
Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&M tool. From version 1.0.0 to before version 2.2.0, the Nezha dashboard exposes two endpoints that create long-lived WebSocket streams to monitored agents: POST /api/v1/terminal → createTerminal() (terminal.go:27-67) and POST /api/v1/file → createFM() (fm.go:28-67). Both call rpc.NezhaHandlerSingleton.CreateStream(streamId, ...) which inserts a new ioStreamContext into an unbounded map[string]*ioStreamContext (s.ioStreams in io_stream.go:59-67). There is no per-user rate limit, no global semaphore, and no per-server connection cap. This issue has been patched in version 2.2.0.
CVSS v3.1
Score 6.5medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Nezha Monitoring, a self-hosted monitoring tool, has a vulnerability (CVE-2026-53522) in versions before 2.2.0 where the endpoints POST /api/v1/terminal and POST /api/v1/file create long-lived WebSocket streams without any per-user rate limiting, global semaphore, or per-server connection caps. These streams are stored in an unbounded map, allowing potential resource exhaustion due to uncontrolled allocation of ioStreamContext objects. This vulnerability corresponds to CWE-770 (Allocation of Resources Without Limits or Throttling). The issue was patched in version 2.2.0.
Potential Impact
The vulnerability allows an attacker with at least low privileges to create unlimited long-lived WebSocket streams, potentially exhausting server resources and causing denial of service. There is no impact on confidentiality or integrity reported. The CVSS 3.1 base score is 6.5 (medium severity), reflecting network attack vector, low attack complexity, low privileges required, no user interaction, unchanged scope, no confidentiality or integrity impact, and high availability impact.
Mitigation Recommendations
Upgrade Nezha Monitoring to version 2.2.0 or later, where this vulnerability has been patched. There is no official vendor advisory provided here, and no temporary mitigations are described. Patch status is not explicitly confirmed but the description states the issue is fixed in 2.2.0, so upgrading is recommended.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-09T17:30:33.456Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a2c7c93e617e2d834c6c81d
Added to database: 06/12/2026, 21:39:31 UTC
Last enriched: 06/20/2026, 16:00:27 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 87
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.