Uninitialized INSTRUX contents returned after decoding failure in pybddisasm
Bitdefender marked the affected products as already unsupported when this CVE was assigned. A patch may not be available. Review the vendor references for migration or mitigation guidance.
This tag describes support at assignment time, not current support for every related product.
Severity and exploitation
KEV coverage does not rule out exploitation.
Assessment vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NSeverity
medium4.8CVSS measures technical severity, not the likelihood of an attack.
Known exploitation
Not listed in the checked CISA KEV catalog
Absence from CISA KEV does not rule out attacks.
Public exploit
Not established by this record
Missing evidence does not mean no public exploit exists.
Remediation
Source guidance available
Review the recorded instructions. Guidance may be a workaround rather than a fixed version.
What this means
The pybddisasm package, version 0.3.0 or lower, has a use of uninitialized memory vulnerability, potentially disclosing process memory when instruction decoding fails. Exploitation requires an application to access the returned object contents after a decoding failure. The package is no longer maintained.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Attack conditions
Exploitation requires an application to access and expose the returned object contents after a decoding failure.
Excerpt from the original source description below.
Review supporting sources →Affected versions
Check the exact model, release, and any platform requirements against your installation.
Bitdefender · Bitdefender
pybddisasm
1 range
Bitdefender · Bitdefender
pybddisasm
Compare with this publisher’s ranges. This does not inspect your installation.
affected
0 → through 0.3.0
python versions
Other versions: unknown
What to do
Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.
Discontinue use of the unmaintained pybddisasm package. No fixed release will become available.
cve.new guidance unless attributed to a publisher. This page does not inspect your installation.
Public exploit evidence
No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.
Original source description
Read the full publisher 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.
References
1 sourcesInside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-118447View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 2
Assigning organization
Additional data publisher
Timeline
All times UTCAdvisory published
Publication date supplied by the source.
Source updated
Latest modification date supplied by the source.
Last imported by cve.new
Latest catalog import, not the date we first saw this advisory.
What changed
Follow changes- CVE · CVE-2026-118447
Observed 2026-11-03T18:52:35.234Z · upstream updated 2026-11-03T18:32:24.225Z
Prioritization updated
before
[]
after
[ { "source": "CISA-ADP", "type": "SSVC", "role": "CISA Coordinator", "timestamp": "2026-11-03T17:23:50.394004Z", "decisions": [ { "name": "Exploitation", "value": "none" }, { "name": "Automatable", "value": "no" }, { "name": "Technical Impact", "value": "partial" } ] } ]
Large field values are marked as truncated previews. Original source snapshots remain retained.
Showing up to 50 most recent observed changes.