CVE-2026-118447
Received Received - Intake

Use of Uninitialized Memory in pybddisasm Python Bindings

Publication date: 2026-11-03

Last updated on: 2026-11-03

Assigner: Bitdefender

Description
A use of uninitialized memory vulnerability in the pybddisasm Python bindings may disclose process memory when instruction decoding fails. The nd_decode, nd_decode_ex, nd_decode_ex2, and nd_decode_with_context functions may return an INSTRUX object whose contents have not been initialized after an unsuccessful decoding operation, including failures caused by invalid parameters. Accessing members of the returned object may expose residual process memory. Exploitation requires an application to access and expose the returned object contents after a decoding failure. 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
CVE-2026-118447
EUVD
EUVD-2026-115701

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-457 The code uses a variable that has not been initialized, leading to unpredictable or unintended results.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves a use of uninitialized memory in the pybddisasm Python bindings. When instruction decoding fails, functions like nd_decode may return an object with uninitialized contents. Accessing this object could expose residual process memory.

Detection Guidance

This vulnerability is specific to applications using the pybddisasm Python library. Detection involves checking if any installed applications use this library and if they handle decoding failures improperly. Review application logs for decoding errors or memory disclosures. No direct commands are provided for detection as it depends on the application context.

Impact Analysis

If exploited, this vulnerability could allow an attacker to read sensitive process memory. This may lead to information disclosure, including potentially confidential or sensitive data. Exploitation requires an application to access and expose the returned object after a decoding failure.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, potentially violating GDPR (data protection) and HIPAA (health information privacy) requirements. Organizations may face compliance risks if this vulnerability exposes personal or health-related data.

Mitigation Strategies

Immediately stop using the pybddisasm library as it is no longer maintained. Update or replace any applications relying on it. If usage is unavoidable, ensure proper error handling to avoid accessing uninitialized memory after decoding failures.

Chat Assistant

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