CVE-2026-118447: medium-severity vulnerability in Bitdefender pybddisasm
Uninitialized INSTRUX contents returned after decoding failure in pybddisasm
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 4.8epss 0.1%
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.
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
Affected products
Bitdefender · pybddisasmRelated CVEs — Bitdefender pybddisasm
In the same product, most dangerous first.
CVE-2026-118448MEDIUMUninitialized output buffer returned after nd_to_text failure in pybddisasmEPSS 0.1%CVE-2026-118446MEDIUMUse-after-free in INSTRUX array members in pybddisasmEPSS 0.1%CVE-2026-118445MEDIUMUse-after-free in INSTRUX structure members in pybddisasmEPSS 0.1%CVE-2026-118444MEDIUMOut-of-bounds reads during instruction decoding in pybddisasmEPSS 0.1%
References
https://pypi.org/project/pybddisasm/