CVE-2026-118446
Received Received - Intake

Use-After-Free in pybddisasm Python Bindings

Vulnerability report for CVE-2026-118446, 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 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 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 affects array-valued members of INSTRUX objects, which are exposed as Python lists. These lists reference memory owned by the parent object. If the parent object is freed but the list or its elements are retained and accessed later, it leads to accessing freed memory. This can cause the Python process to crash or expose process memory.

Detection Guidance

This vulnerability is specific to applications using the pybddisasm Python library. Detection requires checking for applications that use pybddisasm and inspecting their code for improper handling of INSTRUX objects or ND_OPERAND arrays. No direct network detection commands are applicable.

Impact Analysis

The impact includes potential crashes of the Python process using pybddisasm. It may also expose sensitive process memory, which could lead to information disclosure or further exploitation depending on the application context. Exploitation requires retaining and accessing array elements after the parent object is freed.

Mitigation Strategies

Immediately stop using the pybddisasm package as it is no longer maintained. Replace it with an actively maintained alternative for binary disassembly tasks. Audit all applications using pybddisasm to ensure proper memory management of INSTRUX objects and their arrays.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-118446. 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...