CVE-2026-118446: medium-severity vulnerability in Bitdefender pybddisasm
Use-after-free in INSTRUX array members 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 6.9epss 0.1%
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.
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
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-118447MEDIUMUninitialized INSTRUX contents returned after decoding failure 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/