pybddisasm up to 0.3.0 Instruction Decoding uninitialized variable
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.3 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in pybddisasm up to 0.3.0. Impacted is the function nd_decode/nd_decode_ex/nd_decode_ex2/nd_decode_with_context of the component Instruction Decoding. Executing a manipulation can lead to uninitialized variable. This vulnerability only affects products that are no longer supported by the maintainer.
The identification of this vulnerability is CVE-2026-118447. The attack can only be executed locally. There is no exploit available.
Details
A vulnerability has been found in pybddisasm up to 0.3.0 and classified as problematic. This vulnerability affects the function nd_decode/nd_decode_ex/nd_decode_ex2/nd_decode_with_context of the component Instruction Decoding. The manipulation with an unknown input leads to a uninitialized variable vulnerability. The CWE definition for the vulnerability is CWE-457. The code uses a variable that has not been initialized, leading to unpredictable or unintended results. As an impact it is known to affect confidentiality. CVE summarizes:
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.
The advisory is shared for download at pypi.org. This vulnerability was named CVE-2026-118447 since 10/28/2026. The exploitation appears to be easy. The attack needs to be approached locally. There are known technical details, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
Support
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.3
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Uninitialized variableCWE: CWE-457 / CWE-453
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
10/28/2026 CVE reserved11/03/2026 Advisory disclosed
11/03/2026 VulDB entry created
11/03/2026 VulDB entry last update
Sources
Advisory: pypi.orgStatus: Confirmed
CNA: Bitdefender
CVE: CVE-2026-118447 (🔒)
GCVE (CVE): GCVE-0-2026-118447
GCVE (VulDB): GCVE-100-430204
Entry
Created: 11/03/2026 10:25Changes: 11/03/2026 10:25 (65)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.