All vulnerabilities
CVE-2026-102758GHSA-f95g-xc4w-mrcr

The `_nx_secure_x509_asn1_tlv_block_parse()` function parses ASN.1 TLV (tag-length-value) blocks out of DER-encoded data. It is the primitive underneath all X.509 certificate parsing in NetX Secure, a

Eclipse Foundation NetX Duo
CVSS
7.5High
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.17%Chance of exploitation activity in the next 30 days, higher than 6% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in6.5.2.202603Fixed versionGitHub
Published29 Sep 2026Updated 2 Oct 2026CVE List

What fixes it

  • 6.5.2.202603NetX Duo, eclipse threadxGitHub

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

Description

The _nx_secure_x509_asn1_tlv_block_parse() function parses ASN.1 TLV (tag-length-value) blocks out of DER-encoded data. It is the primitive underneath all X.509 certificate parsing in NetX Secure, and therefore runs on certificates supplied by a remote peer during the TLS handshake.

The function reads the one-byte ASN.1 tag from the caller's buffer *before* checking that the buffer holds at least one byte. When a caller passes a remaining length of zero, the guard correctly returns NX_SECURE_X509_ASN1_LENGTH_TOO_LONG, but the read has already happened one byte past the end of the buffer.

code:

nx_secure/src/nx_secure_x509_asn1_tlv_block_parse.c



UINT _nx_secure_x509_asn1_tlv_block_parse(const UCHAR *buffer, ULONG *buffer_length, USHORT *tlv_type,

                                          USHORT *tlv_tag_class, ULONG *tlv_length,
                                          const UCHAR **tlv_data, ULONG *header_length)


{



UINT   current_index;



USHORT current_tag;



ULONG  length;



ULONG  length_bytes;

    current_index = 0;
    current_tag = buffer[current_index];      /* <-- read before the bounds check */
    if (*buffer_length < 1)
    {
        return(NX_SECURE_X509_ASN1_LENGTH_TOO_LONG);
    }

The remainder of the function is correctly ordered. The multi-byte length path is guarded by length_bytes > 4 || length_bytes > *buffer_length before its read loop, the decoded value is checked against length > *buffer_length, and the second single-byte length read follows its own *buffer_length < 1 guard. The tag read is the only load placed ahead of its check.

Text from GitHub Advisory Database

Affected versions 3

  • NetX Duoaffected: all versions through 6.5.1.202602CVE List
  • NetX Duounaffected: 6.5.2.202603CVE List
  • NetX Duo, eclipse threadx<= 6.5.1.202602GitHub

References 1