CVE-2026-118445
Received Received - Intake

Use-After-Free in pybddisasm Python Bindings

Vulnerability report for CVE-2026-118445, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-03

Last updated on: 2026-11-03

Assigner: Bitdefender

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-03
Last Modified
2026-11-03
Generated
2026-11-03
AI Q&A
2026-11-03
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Bitdefender pybddisasm 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-416 The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a use-after-free vulnerability in the pybddisasm Python library. It occurs when a Python object references memory owned by another object (INSTRUX) but does not keep the parent object alive. If the parent object is freed while the reference is still retained, accessing the member leads to use of freed memory. This can cause crashes or expose process memory.

Detection Guidance

This vulnerability is specific to applications using the pybddisasm Python library. Detection requires checking if any applications in your environment use pybddisasm and if they retain references to INSTRUX object members after the parent object is freed. Review application code for improper memory handling patterns.

Impact Analysis

The impact depends on how the vulnerable library is used. If an application retains references to freed memory, it may crash or leak sensitive process memory. Since pybddisasm is no longer maintained, there are no patches, making exploitation risks higher for dependent applications.

Mitigation Strategies

Immediately uninstall or stop using the pybddisasm package as it is no longer maintained. Review and update any applications that depend on it to remove references to INSTRUX object members after parent object freeing. Consider alternative libraries for binary disassembly tasks.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-118445. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...