# CVE-2026-112062: lwIP through 2.2.1 Stack Out-of-Bounds Write via mDNS Search Response Handler

> Adjacent attackers can cause stack buffer overflows and potential code execution by sending malformed mDNS responses to devices using the lwIP library.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-112062, GHSA-7m6v-7jf3-5x4h, UBUNTU-CVE-2026-112062

## What is CVE-2026-112062?

CVE-2026-112062 is a medium-severity memory corruption vulnerability in lwIP, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

lwIP through 2.2.1 contains a stack out-of-bounds write vulnerability in mdns_handle_response that allows adjacent attackers to corrupt stack memory by sending mDNS responses with invalid domain names. Attackers on the local link can send multicast PTR answers with oversized RDLENGTH or SRV answers with RDLENGTH below 6 during a service search, overflowing a 256-byte stack buffer and crashing the device.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2026-112062 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112062 is a medium-severity memory corruption vulnerability in lwIP, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112062 exists.

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

## Sources

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

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