Skip to main content
VulnerabilityPublished

CVE-2026-118446: Use-after-free Vulnerability

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-118446· Medium 6.9

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

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Bitdefender)CVSS 4.06.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
BitdefenderpybddisasmAffected
  • <=0.3.0
Fixed in–
PyPIpybddisasmpkg:pypi/pybddisasmOther threatsAffected
  • <=0.3.0
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.

References

Community reviews

Loading reviews…