Quick answers
- Is CVE-2026-116500 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116500 being exploited in the wild.
- How severe is CVE-2026-116500?
- Medium severity, with a CVSS score of 6.2, published 8 November 2026.
- Which products and versions are affected?
- IBM Qiskit SDK 2.4.0 through 2.6.1.
- Is there a fix for CVE-2026-116500?
- Yes: fixed in Qiskit SDK v2.6.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116500 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-116500?
- Check whether you run IBM Qiskit SDK at an affected version. 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.
How to fix
- Fixed in: Qiskit SDK v2.6.2
Technical details
Unbound recursion in QPY format deserialization (qiskit.qpy.load() function) for format versions ≥13 allows processing of maliciously crafted payloads to exceed stack limits and trigger segmentation faults. The vulnerability affects deserialization of untrusted QPY data with no authentication or special permissions required; local attacker access is necessary. A fix is available in version 2.6.2.
Affected products
- IBM Qiskit SDK 2.4.0 through 2.6.1
Timeline
- 2026-11-05: disclosed