Application crash via unbounded WebSocket thread creation
Published Apr 3, 2026 · Updated Apr 3, 2026
Uncontrolled resource consumption in Mesop 1.2.3 through versions before 1.2.5 allows remote attackers to crash applications via WebSocket floods. The handle_websocket function in mesop/server/server.py starts a new threading.Thread for every parsed ui_request without a pool, queue, backpressure, or per-connection limit. A single unauthenticated connection can exhaust operating-system threads and memory, making the entire Mesop application unavailable.
Summary
What happened
Uncontrolled resource consumption in Mesop 1.2.3 through versions before 1.2.5 allows remote attackers to crash applications via WebSocket floods. The handle_websocket function in mesop/server/server.py starts a new threading.Thread for every parsed ui_request without a pool, queue, backpressure, or per-connection limit. A single unauthenticated connection can exhaust operating-system threads and memory, making the entire Mesop application unavailable.
The record
- CVE
- CVE-2026-34824
- Published
- Apr 3, 2026
- Updated
- Apr 3, 2026
- Vendor
- mesop-dev
- Product
- Mesop
- Classifications
- CWE-770, CWE-400, CWE-125, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 3, 2026CVE publishedPublication date reported by the CVE source.
- Apr 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 1.2.3, < 1.2.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-3jr7-6hqp-x679 WebSocket flood PoCfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo