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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 4
- StatusAwaiting Analysis → PublishedNVD modified 2026-10-31 01:59
- StatusPublished → Awaiting AnalysisNVD modified 2026-10-27 16:03
- StatusReceived → PublishedNVD modified 2026-10-26 21:52
- First seenCVSS 4.8NVD modified 2026-10-26 22:16
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 6
- https://github.com/davea42/libdwarf-code
- https://github.com/davea42/libdwarf-code/blob/v2.3.3/src/lib/libdwarf/dwarf_debugaddr.c#L175-L216
- https://github.com/davea42/libdwarf-code/commit/71f04013ddc2a3c88b9e25a4162ee2824741b593
- https://github.com/davea42/libdwarf-code/issues/336
- https://hackmd.io/@haindpwn/libdwarf-debug-addr-table-section-offset-oob-read
- https://www.vulncheck.com/advisories/libdwarf-through-2.3.3-heap-out-of-bounds-read-via-dwarf-debug-addr-table