CVE-2026-116732 davea42 CVE debrief

Who should care

Defenders responsible for software development, vulnerability management, and incident response should be aware of this vulnerability. Specifically, those using or managing systems that utilize libdwarf should assess their exposure and take necessary actions to mitigate the risk.

Why it matters

Defenders should prioritize verifying and patching libdwarf installations to prevent potential crashes or information disclosure. This vulnerability can be exploited by supplying a crafted object file, highlighting the need for careful validation and updating of affected software.

• Potential crashes or instability in applications using libdwarf
• Information disclosure through adjacent heap byte exposure

Technical summary

The libdwarf library through version 2.3.3 is vulnerable to a heap out-of-bounds read in the dwarf_debug_addr_table() function. This vulnerability occurs when the function omits the table starting offset during validation of the .debug_addr unit length. An attacker can exploit this by providing a crafted object file with a non-zero offset table, which causes dwarf_debug_addr_by_index() to read beyond the heap buffer. This can lead to the disclosure of adjacent heap bytes or crashes in consumer applications.

Defensive priority

Defenders should prioritize verifying and patching libdwarf installations to prevent potential crashes or information disclosure.

Recommended defensive actions

• Verify libdwarf version and apply patches if necessary
• Review and update affected software installations
• Monitor for potential exploitation attempts
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description, affected versions, and references to additional information. The libdwarf library through version 2.3.3 is vulnerable to a heap out-of-bounds read in the dwarf_debug_addr_table() function. This vulnerability occurs when the function omits the table starting offset during validation of the .debug_addr unit length. An attacker can exploit this by providing a crafted object file with a non-zero offset table, which causes dwarf_debug_addr_by_

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.