# CVE-2026-32746: Memory corruption in inetutils

> An out-of-bounds write in GNU inetutils telnetd allows attackers to execute arbitrary code or cause a denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Mar 2026
- **Updated:** 23 Mar 2026
- **Also known as:** DEBIAN-CVE-2026-32746, GHSA-qvfm-56cp-4988, MGASA-2026-0122, SUSE-SU-2026:0930-1, UBUNTU-CVE-2026-32746, openSUSE-SU-2026:10657-1, openSUSE-SU-2026:20374-1

## What is CVE-2026-32746?

CVE-2026-32746 is a critical memory corruption vulnerability in GNU inetutils, published on 13 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

telnetd in GNU inetutils through 2.7 allows an out-of-bounds write in the LINEMODE SLC (Set Local Characters) suboption handler because add_slc does not check whether the buffer is full.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `krb5-appl` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 1.0.3-3.12.1 |
| `krb5-appl` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 1.0.3-3.12.1 |
| `krb5-appl` | openSUSE:Leap 16.0 | All versions | 1.0.3-bp160.2.1 |
| `krb5-appl` | openSUSE:Tumbleweed | All versions | 1.0.3-6.1 |

Products: Gnu Inetutils.

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

Apply the vendor's patch.

## Is CVE-2026-32746 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32746 exists.

Public exploit code:

- CVE-2026-32746 - GNU InetUtils telnetd LINEMODE SLC Buffer Overflow PoC (pre-auth RCE, CVSS 9.8) (github_poc): https://github.com/jeffaf/cve-2026-32746
- https://github.com/watchtowrlabs/watchtowr-vs-telnetd-CVE-2026-32746 (github_poc): https://github.com/watchtowrlabs/watchtowr-vs-telnetd-CVE-2026-32746
- Kangaroo is a exploit built on CVE-2026-32746.  i made this for security researchers, IT professionals, DevOps. so they can understand it better. DO NOT USE THIS FOR ILLEGAL USE, IF YOU DO... YOU MAY BE SUBJECT TO ARREST, AND FINES. (github_poc): https://github.com/MonkeySeC-sys/Kangaroo
- https://github.com/duduLiu8787/CVE-2026-32746-Exploit (github_poc): https://github.com/duduLiu8787/CVE-2026-32746-Exploit
- https://github.com/danindiana/cve-2026-32746-mitigation (github_poc): https://github.com/danindiana/cve-2026-32746-mitigation
- https://github.com/chosenonehacks/CVE-2026-32746 (github_poc): https://github.com/chosenonehacks/CVE-2026-32746

## Other vulnerabilities in GNU inetutils

- [CVE-2023-40303](https://insights.sbomify.com/CVE-2023-40303/): Privilege escalation in n/a (high 7.8)
- [CVE-2026-28372](https://insights.sbomify.com/CVE-2026-28372/): Privilege escalation in inetutils (high 7.4)
- [CVE-2026-32772](https://insights.sbomify.com/CVE-2026-32772/): Information disclosure in inetutils (low 3.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-32746 is a critical memory corruption vulnerability in GNU inetutils, published on 13 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32746 exists.

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

## Sources

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

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