In Eclipse ThreadX NetX Duo versions 6.0 through 6.5.2.202603, the NetX Secure DTLS server never compares the cookie a client returns with the one it issued, and treats any non-empty cookie as verified. A remote attacker can make the server send its full handshake flight, several kilobytes, to a forged source address, using it to reflect amplified traffic at a third party.
0.4%(unchanged from 0.4% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 32nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-290Authentication Bypass by Spoofing CWE-406Insufficient Control of Network Message Volume (Network Amplification)
Show the promptExplain CVE-2026-106465 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-106465?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-106465?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-106465 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
eclipse foundation:eclipse threadx netx duo
Versions
From the CNA's record in the CVE List.
Product
Affected
Eclipse Foundation Eclipse ThreadX NetX Duo
from 6.0 through 6.5.2.202603
Attack patterns (CAPEC)
CAPEC-21 Exploitation of Trusted Identifiers Likelihood: High · Severity: High
CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
CAPEC-59 Session Credential Falsification through Prediction Likelihood: High · Severity: High
CAPEC-60 Reusing Session IDs (aka Session Replay) Likelihood: High · Severity: High
CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
CAPEC-461 Web Services API Signature Forgery Leveraging Hash Function Extension Weakness Severity: High