# CVE-2026-106465: Security feature bypass in NetX Duo

> Attackers can bypass DTLS cookie verification in NetX Duo, allowing handshakes from forged source addresses without return-routability checks.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-7c5f-gmpm-f655

## What is CVE-2026-106465?

CVE-2026-106465 is a high-severity vulnerability in Eclipse Foundation NetX Duo, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The NetX Secure DTLS server sends a HelloVerifyRequest carrying a freshly generated cookie, but never checks the cookie a client returns. The ClientHello parser copies the client's cookie bytes over the value the server issued, and the server then decides whether the client has been verified from the cookie's length alone. A peer that puts any single cookie byte in its first ClientHello skips the verification exchange entirely, so the server has no return-routability check and completes handshakes for forged source addresses.

Weakness: CWE-406 (Insufficient Control of Network Message Volume (Network Amplification)), CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2026-106465?


## How do I fix CVE-2026-106465?

No fix has been published for CVE-2026-106465 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-106465 being exploited?

There is no known exploitation of CVE-2026-106465 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-106465 and fix it if it is affected.

What it is: CVE-2026-106465 is a high-severity vulnerability in Eclipse Foundation NetX Duo, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-106465 in the wild and no public exploit code.

Affected product: Eclipse Foundation NetX Duo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-106465/ (Markdown: https://insights.sbomify.com/CVE-2026-106465/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-106465
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-106465
- OSV: https://osv.dev/vulnerability/CVE-2026-106465

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-106465/
Summaries are generated and may contain mistakes; the official description above is the record.