# CVE-2026-93652: Integer Overflow or Wraparound in µD3TN

> Remote attackers can cause a denial of service in µD3TN via an integer overflow in the TCPCLv3 handshake leading to heap overflow.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-mf4m-237x-h46p

## What is CVE-2026-93652?

CVE-2026-93652 is a high-severity vulnerability in µD3TN, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Integer overflow in µD3TN v0.15.0 TCPCLv3 handshake causes heap overflow, allowing remote attackers to reliably cause DoS

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


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

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

## Is CVE-2026-93652 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93652 is a high-severity vulnerability in µD3TN, published on 18 Sep 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-93652 in the wild and no public exploit code.

Affected product: µD3TN. 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-93652/ (Markdown: https://insights.sbomify.com/CVE-2026-93652/index.md)
```

## Sources

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

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