Live › vulnerability › CVE-2026-92843
Go to dashboardNetX Secure's TLS 1.3 Certificate parser reads the per-certificate extensions_length unchecked; if it exceeds the remaining list, total_length underflows and the parser reads up to ~64 KiB past the buffer, pre-authentication, reachable by a rogue server, on-path attacker or rogue AP. Vendor-confirmed impact is a silent over-read or fault (DoS); bytes go to the DER parser, not back to the attacker. The same underflow could make the bad cert_length a copy size (possible out-of-bounds write); the vendor has not confirmed this. No known exploitation or public PoC.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| NetX Duo (Eclipse ThreadX) | vendor | <= 6.5.1.202602 | 6.5.2.202603 |
6.5.1.202602 built with NX_SECURE_TLS_TLS_1_3_ENABLED, as a client or as a server that verifies client certificates6.5.2.202603, then rebuild and reflashEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
A missing bounds check in the TLS 1.3 Certificate-message parser of NetX Secure lets a malicious TLS 1.3 server trigger an unsigned-integer underflow and a subsequent heap out-of-bounds read in any peer that processes a remote Certificate message. It is reachable pre-authentication, during the normal handshake, before certificate verification completes.
This page as .md · .json · in your agent: get_signal("CVE-2026-92843")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.