CVE-2026-118445

Use-after-free in INSTRUX structure members in pybddisasm

  • Medium 6.9

Description

A use-after-free vulnerability in the pybddisasm Python bindings affects structure-valued members of INSTRUX objects. These members are exposed through Python objects that reference memory owned by the parent INSTRUX object. A retained reference to a member does not keep the parent allocation alive. Accessing the member after the parent INSTRUX object has been freed therefore accesses freed memory. Depending on how the member 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 a member reference after the parent object has been freed. The pybddisasm package is no longer maintained.

Key facts

Published
3 Nov 2026
Last changed
3 Nov 2026
Assigned by
Bitdefender
EPSS
0.105% likely to be exploited in the next 30 days, higher than 1.067% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 6.9CVSS 4.0, Mediumfrom the CNA (Bitdefender)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

What to do

  • Discontinue use of the unmaintained pybddisasm package. No fixed release will become available.CNA solution statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Bitdefenderpybddisasm
  • Default status: unknown
  • 0 up to and including 0.3.0 (affected)

Timeline

  1. 3 Nov 2026 Published

Weakness

References