# CVE-2026-119053: lwIP 2.0.0 through 2.2.1 SNMP Agent Out-of-Bounds Read via snmp_pbuf_stream_writeto()


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-119053, GHSA-mm46-vrwc-xmpq

## What is CVE-2026-119053?

CVE-2026-119053 is a medium-severity vulnerability in lwIP, published on 29 Oct 2026. 

### Official description

lwIP 2.0.0 through 2.2.1 built with the SNMP agent contains an out-of-bounds read vulnerability in snmp_pbuf_stream_writeto() that bounds copies by pbuf->len instead of remaining bytes. Remote unauthenticated attackers knowing the read community can send fragmented SNMP requests to receive adjacent receive-buffer or pool memory echoed in responses.

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

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


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

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

## Is CVE-2026-119053 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119053 is a medium-severity vulnerability in lwIP, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119053 in the wild and no public exploit code.

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

## Sources

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

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