PT-2026-59666 — Pypi Qiskit

PT-2026-59666 · Pypi · Qiskit

Publicado

2026-07-13

Atualizado

2026-07-13

CVSS v3.1

8.6

Alta

Vetor

AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H

Impact

A maliciously crafted QPY file containing a malformed symengine serialization stream as part of the larger QPY serialization of a ParameterExpression object can cause a segfault within the symengine library, allowing an attacker to terminate the hosting process deserializing the QPY payload.

Patches

This issue is addressed in 1.3.0 when using QPY format version 13. QPY format versions 10, 11, and 12 are all still inherently vulnerable if they are using symengine symbolic encoding and symengine <= 0.13.0 is installed in the deserializing environment (as of publishing there is no newer compatible release of symengine available). Using QPY 13 is strongly recommended for this reason.

The symengine 0.14.0 release has addressed the segfault issue, but it is backward incompatible and will not work with any Qiskit release; it also prevents loading a payload generated with any other version of symengine. Using QPY 13 is strongly recommended for this reason.

It is also strongly suggested to patch the locally installed version of symengine in the deserializing environment to prevent the specific segfault. The commit [1] can be applied on top of symengine 0.13.0 and used to build a patched python library that will not segfault in the presence of a malformed payload and instead raise a RuntimeError which will address the vulnerability.

Workarounds

As QPY is backwards compatible qiskit.qpy.load() function will always attempt to deserialize the symengine-serialized payloads in QPY format versions 10, 11, and 12. These are any payloads generated with the use symengine argument on qiskit.qpy.dump() set to True (which is the default value starting in Qiskit 1.0.0. The only option is to disallow parsing if those QPY formats are being read and the use symengine flag was set in the file's header. You can detect whether a payload is potentially vulnerable by using the following function built using the Python standard library:

python

import struct
from collections import namedtuple


def check qpy payload(path: str) -> bool:
  """Function to check if a QPY payload is potentially vulnerable to a symengine vulnerability.

  Args:
    path: The path to the QPY file

  Returns:
    Whether the specified payload is potentially vulnerable. If ``True`` the conditions for
    being vulnerable exist, however the payload may not be vulnerable it can't be detected
    until trying to deserialize.
  """
  with open(path, "rb") as file obj:
    version = struct.unpack("!6sB", file obj.read(7))[1]
    if version < 10 or version >= 13:
      return False
    file obj.seek(0)
    header tuple = namedtuple(
      "FILE HEADER",
      [
        "preface",
        "qpy version",
        "major version",
        "minor version",
        "patch version",
        "num programs",
        "symbolic encoding",
      ],
    )
    header pack str = "!6sBBBBQc"
    header read size = struct.calcsize(header pack str)
    data = struct.unpack(header pack str, file obj.read(header read size))
    header = header tuple(*data)
    return header.symbolic encoding == b"e"

Note, this function does not tell you whether the payload is malicious and will cause the segfault, just that conditions for it to be potentially malicious exist. It's not possible to know ahead of time whether symengine will segfault until the data is passed to that library.

References

[1] https://github.com/symengine/symengine/commit/eb3e292bf13b2dfdf0fa1c132944af8df2bc7d51

Correção

Encontrou algum problema na descrição? Tem algo a acrescentar? Fique à vontade para nos escrever 👾

dbugs@ptsecurity.com

Identificadores relacionados

PYSEC-2026-3045

Produtos afetados

Qiskit