Live › vulnerability › CVE-2026-118447
The pybddisasm Python bindings can return an instruction object with uninitialized contents when decoding fails. An application that reads and exposes that object after a failed decode can leak residual process memory.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 09:19 UTC. All times on this page are UTC.
Only applications that import pybddisasm and expose the INSTRUX object returned after a failed decode are exposed. The sources say exploitation requires the application to access and expose those contents, so a program that only decodes valid input or never shows the result is not exposed. The package is no longer maintained, so the sources state no fixed version.
No product ranges from the sources yet.
pybddisasm is installed in any environment, for example with pip show pybddisasm.nd_decode, nd_decode_ex, nd_decode_ex2 or nd_decode_with_context whose returned object is logged, returned to users or otherwise exposed after a failed decode.No fix yet, per the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-118447")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.