# CVE-2026-116732: libdwarf through 2.3.3 Heap Out-of-Bounds Read via dwarf_debug_addr_table


- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** AZL-111131, DEBIAN-CVE-2026-116732, GHSA-8mx3-4rwx-rhjv

## What is CVE-2026-116732?

CVE-2026-116732 is a medium-severity vulnerability in davea42 libdwarf, published on 26 Oct 2026. 

### Official description

libdwarf through 2.3.3 contains a heap out-of-bounds read vulnerability in dwarf_debug_addr_table() that omits the table starting offset when validating .debug_addr unit length. Attackers can supply a crafted object file with a non-zero offset table, causing dwarf_debug_addr_by_index() to read past the heap buffer, disclosing adjacent heap bytes or crashing consumers.

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

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


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

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

## Is CVE-2026-116732 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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