CVE-2026-118447
MediumCVSS 4.8Summary
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 with uninitialized contents after an unsuccessful decoding operation, and accessing its members may expose residual process memory.
Risk Assessment
Residual process memory may leak or the application may crash. The risk occurs when an application accesses and exposes the returned object contents after a decoding failure.
Recommendation
Replace pybddisasm with a maintained alternative or restrict its use, as the package is no longer maintained. Applications should check decoding results and avoid using the INSTRUX object after a failure.
Other vulnerabilities in pybddisasm
See all- CVE-2026-118448Medium
A use of uninitialized memory vulnerability in the pybddisasm Python bindings affects nd_to_text. If text conversion fails, including due to invalid parameters, the output buffer may remain uninitialized while still being converted into a Python return value, potentially disclosing residual process memory or crashing the Python process.
- CVE-2026-118446Medium
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 referencing memory owned by the parent INSTRUX object, and retaining an element does not keep the parent allocation alive, so accessing it after the parent is freed accesses freed memory.
- CVE-2026-118445Medium
A use-after-free vulnerability in the pybddisasm Python bindings affects structure-valued members of INSTRUX objects. These members are exposed through Python objects referencing memory owned by the parent INSTRUX object, and a retained reference does not keep the parent allocation alive, so accessing the member after the parent is freed accesses freed memory.
- CVE-2026-118444Medium
Out-of-bounds read vulnerabilities in the pybddisasm Python bindings may disclose adjacent process memory during instruction decoding. The nd_decode function may read up to 15 bytes without checking the actual buffer length, and nd_decode_ex, nd_decode_ex2, and nd_decode_with_context pass the caller-supplied size without validating it against the actual buffer length, potentially exposing data via nd_get_instrux_bytes.
Original NVD description (English source)
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.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS