# CVE-2026-132049: Lldpd: lldpd: out-of-bounds read in liblldpctl on a short lldp-med location


- **Severity:** Medium 4.3 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-132049, GHSA-7j9v-8pvh-5rmm, UBUNTU-CVE-2026-132049

## What is CVE-2026-132049?

CVE-2026-132049 is a medium-severity vulnerability in lldpd, published on 18 Nov 2026. 

### Official description

A flaw was found in lldpd. The service fails to verify that Link Layer Discovery Protocol - Media Endpoint Discovery (LLDP-MED) location records received from network neighbors match their declared lengths. An adjacent attacker on the local network can exploit this flaw by sending crafted packets, causing client applications using the liblldpctl library to read past buffer boundaries when parsing location data. This issue can lead to an information disclosure of adjacent process memory.

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

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

It affects 1 product.


Products: Red Hat Enterprise Linux.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:redhat:enterprise_linux:10:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:enterprise_linux:8:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:enterprise_linux:9:*:*:*:*:*:*:*`

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

Upgrade to a fixed version.

## Is CVE-2026-132049 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-132049 is a medium-severity vulnerability in lldpd, published on 18 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-132049 exists.

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

## Sources

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

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