Memory corruption via unbounded RSA modulus
Published Oct 20, 2026 · Updated Oct 20, 2026
X.509 buffer overflow in Eclipse ThreadX NetX Duo allows remote attackers to corrupt memory via oversized RSA certificate keys. NetX Secure accepts unchecked modulus lengths and writes signature-verification results into fixed-size static buffers. TLS/DTLS clients verifying server chains and servers requesting client certificates are exposed before authentication; a specific exploitation path is not established.
Summary
What happened
X.509 buffer overflow in Eclipse ThreadX NetX Duo allows remote attackers to corrupt memory via oversized RSA certificate keys. NetX Secure accepts unchecked modulus lengths and writes signature-verification results into fixed-size static buffers. TLS/DTLS clients verifying server chains and servers requesting client certificates are exposed before authentication; a specific exploitation path is not established.
The record
- CVE
- CVE-2026-93475
- Published
- Oct 20, 2026
- Updated
- Oct 20, 2026
- Vendor
- The Eclipse Foundation
- Product
- Eclipse ThreadX NetX Duo
- Classifications
- CWE-1284, CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 20, 2026CVE publishedPublication date reported by the CVE source.
- Oct 20, 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=0 <=6.5.1.202602
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us