# CVE-2026-120596: CVE-2026-120596


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Nov 2026
- **Updated:** 2 Nov 2026
- **Also known as:** GHSA-mg75-66wv-hfxw

## What is CVE-2026-120596?

CVE-2026-120596 is a high-severity vulnerability in Ethernut / egnite GmbH Nut/Net TCP/IP Stack, published on 2 Nov 2026. 

### Official description

A remotely exploitable denial-of-service vulnerability exists in the TCP options parser of the Nut/Net TCP/IP stack included in Nut/OS, developed by Ethernut/Egnite. Nut/OS releases up to version 5.1 are affected. An unauthenticated attacker can send a single TCP segment containing an unknown TCP option with a length byte of zero to any open TCP port on a vulnerable device. When processed, this malformed option triggers an infinite loop in the function NutTcpInputOptions, permanently blocking the TCP processing thread and rendering all TCP-based services unresponsive until the device is rebooted.

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

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


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

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

## Is CVE-2026-120596 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120596 is a high-severity vulnerability in Ethernut / egnite GmbH Nut/Net TCP/IP Stack, published on 2 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120596 in the wild and no public exploit code.

Affected product: Ethernut / egnite GmbH Nut/Net TCP/IP Stack. 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-120596/ (Markdown: https://insights.sbomify.com/CVE-2026-120596/index.md)
```

## Sources

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

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