Qiskit SDK is vulnerable when deserializing QPY Files and may overflow the available stack space.

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps IBM/Qiskit SDK (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for IBM/Qiskit SDK.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Sep 3, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 3, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 3, 2026

Sources and claim methodology

• Source referenceibm.com

Related CVEs

• c-ares : Use-after-free / double-free in c-ares query-completion handling, remotely triggerable via ares_getaddrinfo() over TCPSame generic ecosystem
• Medplum - Exposure of OAuth client secret via dynamic registration endpoint in self-hosted configurationsSame generic ecosystem
• Medplum - Improper Validation of Redirect URI in External Auth Callback allows Authorization Code LeakageSame generic ecosystem
• toml-node: Prototype Pollution Leads to `Object.prototype` Corruption via `__proto__` Key-Path DesynchronizationSame generic ecosystem
• stream-json: pick/ignore/filter/replace filters are O(depth²) on nested input — small crafted JSON blocks the event loop for seconds→minutes (DoS)Same generic ecosystem
• toml-node: Uncontrolled RecursionSame generic ecosystem