PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-93475 Eclipse Foundation CVE debrief

A critical vulnerability exists in the X.509 parser of NetX Secure, part of Eclipse ThreadX - NetX Duo. The parser accepts RSA public keys of any size but decrypts them into fixed-size buffers, leading to an out-of-bounds write when encountering a certificate with a larger modulus. This issue is reachable pre-authentication and can be triggered during TLS or DTLS client verification of a malicious server's chain or during server-performed client-certificate authentication.

Vendor
Eclipse Foundation
Product
Eclipse ThreadX - NetX Duo
CVSS
CRITICAL 9.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-20
Original CVE updated
2026-10-20
Advisory published
2026-10-20
Advisory updated
2026-10-20

Who should care

Defenders responsible for systems using NetX Secure X.509 for TLS or DTLS authentication should assess exposure and prioritize remediation. This includes roles managing network security, system administrators, and cybersecurity teams.

Why it matters

CVE-2026-93475 is a critical vulnerability in NetX Secure X.509 that allows for out-of-bounds writes via unbounded RSA moduli. Defenders should verify exposure, prioritize remediation, and review secure communication configurations to prevent potential attacks.

  • Potential for pre-authentication attacks on TLS or DTLS connections.
  • Possible disruption of secure communication channels.
  • Need for immediate verification of exposure and remediation.
  • Requirement for careful review and update of TLS or DTLS client and server configurations.

Technical summary

The X.509 parser in NetX Secure accepts RSA public keys of any size but decrypts them into fixed-size buffers. A certificate with a larger modulus causes an out-of-bounds write during ordinary certificate-chain verification. This is reachable pre-authentication and can be triggered during TLS or DTLS client verification of a malicious server's chain or during server-performed client-certificate authentication.

Defensive priority

Immediate verification of exposure and remediation is recommended for systems using NetX Secure X.509 for TLS or DTLS authentication.

Recommended defensive actions

  • Verify exposure by checking the version of NetX Duo in use and determining if it falls within the affected range.
  • Upgrade to version 6.5.2.202603 or later if currently using a vulnerable version.
  • Implement compensating controls such as restricting access to critical systems or monitoring for suspicious activity.
  • Review and update TLS or DTLS client and server configurations to ensure secure authentication mechanisms are in place.
  • Perform asset inventory to identify all systems using NetX Secure X.509 for TLS or DTLS authentication.
  • Monitor for suspicious activity related to TLS or DTLS connections.
  • Track and document remediation progress for auditing and compliance purposes.

Evidence notes

The CVE record and source item provide details on the vulnerability, including its impact on NetX Secure X.509 and potential attack vectors. However, specific details about exploitation and affected versions are limited.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-93475 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-93475

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-93475 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-93475

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.