CVE-2026-116732

libdwarf through 2.3.3 Heap Out-of-Bounds Read via dwarf_debug_addr_table

Published Oct 26, 2026 CVSS 4.0 · 4.8 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

A heap out‑of‑bounds read occurs in the libdwarf debugging library when dwarf_debug_addr_table processes a .debug_addr section that contains a non‑zero starting offset. Because the offset is omitted during length validation, dwarf_debug_addr_by_index can read past the allocated buffer, exposing adjacent heap data or causing a crash. The flaw is rated CVSS 4.8, indicating a moderate risk to confidentiality, integrity, and availability.

Affected Systems

The issue affects the libdwarf library, up to version 2.3.3, released by davea42. Applications that link against this library – such as debuggers, profilers, and other tools that parse DWARF debugging information – can process object files containing a malformed .debug_addr section. The vulnerability is inherent in the library’s implementation and not tied to a specific operating system or architecture, so any build that includes these versions is potentially impacted.

Risk and Exploitability

An attacker must supply a crafted object file with a non‑zero .debug_addr offset to a process that uses libdwarf. The read‑only nature of the flaw means there is no direct code execution path, but the exposed data can leak sensitive information and the failure can lead to a denial of service. The EPSS score is not available and the vulnerability is not listed in the CISA KEV catalog, but the realistic attack vector—loading malicious binaries—makes exploitation plausible in development and debugging environments.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Check for the latest release of libdwarf and upgrade if a newer version contains the fix for the out‑of‑bounds read.
  • In the code that loads object files, verify that the .debug_addr section starts at offset 0; reject any files that do not meet this requirement before calling dwarf_debug_addr_table.
  • Run applications that depend on libdwarf inside a sandbox or memory‑isolated process so that any read beyond the intended bounds or resulting crashes cannot affect the rest of the system.
  • If possible, enable runtime bounds checking or employ a memory protection framework (e.g., ASan, AddressSanitizer) to detect and contain any unexpected memory access during development and testing.

Generated by OpenCVE AI on October 27, 2026 at 08:12 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title libdwarf through 2.3.3 Heap Out-of-Bounds Read via dwarf_debug_addr_table
First Time appeared Libdwarf Project
Libdwarf Project libdwarf
Weaknesses CWE-125
CPEs cpe:2.3:a:libdwarf_project:libdwarf:*:*:*:*:*:*:*:*
Vendors & Products Libdwarf Project
Libdwarf Project libdwarf
References
Metrics cvssV3_1

{'score': 4.4, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L'}

cvssV4_0

{'score': 4.8, 'vector': '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'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 31, 2026, 1:59 AM
Reserved
Oct 26, 2026, 8:23 PM
Status
Awaiting Analysis
Published
Oct 26, 2026, 10:16 PM
Modified
Oct 31, 2026, 2:17 AM
Severity
Moderate
Public date
Oct 26, 2026, 9:52 PM