# CVE-2026-106026: tftp-hpa 5.4 before 6.0 Out-of-Bounds Read via tftpd Remap Jump Rule

> Unauthenticated attackers can crash the TFTP server by sending requests matching remap jump rules, requiring specific remap configuration.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-106026, GHSA-w9pp-27r4-r6rj, UBUNTU-CVE-2026-106026

## What is CVE-2026-106026?

CVE-2026-106026 is a medium-severity memory corruption vulnerability in H. Peter Anvin tftp-hpa, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

tftp-hpa 5.4 before 6.0 contains an out-of-bounds read vulnerability in rewrite_string() in tftpd/remap.c that walks heap memory during jump label searches. Unauthenticated remote attackers can send read or write requests whose filename matches a remap jump rule to crash the forked in.tftpd request handler.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

Upgrade to a fixed version.

## Is CVE-2026-106026 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-106026 is a medium-severity memory corruption vulnerability in H. Peter Anvin tftp-hpa, published on 6 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-106026 in the wild and no public exploit code.

Affected product: H. Peter Anvin tftp-hpa. 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-106026/ (Markdown: https://insights.sbomify.com/CVE-2026-106026/index.md)
```

## Sources

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

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