CVE-2026-118446: Use-after-free Vulnerability
Source GCVE Database
Not known to be exploited · CVSS 6.9 Medium · end of life, no fix coming : replace or isolate pybddisasm; no fix will be released.
Data as of 3 Nov 2026, 10:43 UTC
Thin evidence
One scorer or none| CNA (Bitdefender) | CVSS 4.0 | 6.9 |
|---|
- Patch
- None coming – the product is end of life
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
No fix will be released: pybddisasm is end of life. Replace it, or isolate it from untrusted networks until you can.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Bitdefenderpybddisasm | Affected
| Fixed in– |
PyPIpybddisasmpkg:pypi/pybddisasmOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should avoid retaining references to array elements of INSTRUX objects after the parent object is freed. Consider using alternative maintained libraries or updating application logic to prevent use-after-free conditions involving these objects.
Description
CVE-2026-118446 is a use-after-free vulnerability in the pybddisasm Python bindings affecting array-valued members of INSTRUX objects, such as ND_OPERAND arrays. These arrays are exposed as Python lists referencing memory owned by the parent INSTRUX object. Retaining references to list elements after the parent object is freed can lead to accessing freed memory, potentially causing crashes or exposure of process memory. Exploitation requires specific application behavior retaining and accessing these elements post-free. The pybddisasm package is no longer maintained.