Quick answers
- Is CVE-2026-118448 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118448 being exploited in the wild.
- How severe is CVE-2026-118448?
- Informational severity, published 3 November 2026.
- Which products and versions are affected?
- pybddisasm pybddisasm.
- Is there a fix for CVE-2026-118448?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-118448 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-118448?
- Check whether you run Pybddisasm. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A use-of-uninitialized-memory flaw exists in the pybddisasm Python bindings' nd_to_text function. When the underlying text conversion fails—particularly due to invalid parameters—the output buffer remains uninitialized but is still returned as a Python value. An application that invokes nd_to_text with inputs that cause conversion to fail, then uses or returns the result, could leak residual process memory or trigger a crash.
Affected products
- pybddisasm pybddisasm
Timeline
- 2026-11-03: disclosed