CVE-2026-97152
8.6Nanomsg · Nanomsg
Nanomsg contains a heap-based buffer overflow in the WebSocket transport layer, triggered by an unchecked copy of the Sec-WebSocket-Version header, allowing for potential remote code execution.
Executive summary
A heap-based buffer overflow vulnerability in Nanomsg versions prior to 1.2.3 poses a severe risk of remote code execution and system compromise.
Vulnerability
This vulnerability is a heap-based buffer overflow (CWE-122) occurring within the WebSocket transport mechanism. An authenticated remote attacker can trigger this flaw by sending a specially crafted Sec-WebSocket-Version header, which is processed via an unchecked snprintf operation.
Business impact
The presence of this vulnerability creates a significant risk of unauthorized code execution, which could lead to a complete compromise of the affected application or underlying server. With a CVSS score of 8.6, this issue is classified as high severity, indicating that successful exploitation could result in the loss of data confidentiality, integrity, and availability. Organizations relying on Nanomsg for network communications should prioritize remediation to prevent potential service disruption or lateral movement by an attacker.
Remediation
Immediate Action: Upgrade to Nanomsg version 1.2.3 or higher immediately to resolve the vulnerable memory handling logic.
Proactive Monitoring: Monitor network traffic for malformed WebSocket headers or unusual memory spikes in applications utilizing the Nanomsg library.
Compensating Controls: Implement strict input validation on all WebSocket headers at the application gateway or Web Application Firewall (WAF) level to block requests containing anomalous header lengths or characters.
Exploitation status
Public Exploit Available: Unknown
Analyst recommendation
Given the high CVSS score and the critical nature of memory corruption vulnerabilities, organizations must treat this as a priority update. Administrators should verify the version of Nanomsg currently deployed and perform an immediate upgrade to 1.2.3. If upgrading is not immediately feasible, consider migrating to the NNG library, which the vendor identifies as being specifically hardened for operation in hostile network environments.
History
- Disclosed CVE record published
- Collected by CVE Brief via github
- Analyst report written
- Published in the daily brief high section