Deserialization of Untrusted Data The advisory has been revoked - it doesn't affect any version of package openshift-service-mesh/istio-operator-bundle  (opens in a new tab)


Threat Intelligence

EPSS
16.9% (97th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL8-OPENSHIFTSERVICEMESHISTIOOPERATORBUNDLE-15058737
  • published22 Jan 2026
  • disclosed20 Jan 2026

Introduced: 20 Jan 2026

CVE-2025-56005  (opens in a new tab)
CWE-502  (opens in a new tab)

Amendment

The Red Hat security team deemed this advisory irrelevant for RHEL:8.

NVD Description

Note: Versions mentioned in the description apply only to the upstream openshift-service-mesh/istio-operator-bundle package and not the openshift-service-mesh/istio-operator-bundle package as distributed by RHEL.

An undocumented and unsafe feature in the PLY (Python Lex-Yacc) library 3.11 allows Remote Code Execution (RCE) via the picklefile parameter in the yacc() function. This parameter accepts a .pkl file that is deserialized with pickle.load() without validation. Because pickle allows execution of embedded code via __reduce__(), an attacker can achieve code execution by passing a malicious pickle file. The parameter is not mentioned in official documentation or the GitHub repository, yet it is active in the PyPI version. This introduces a stealthy backdoor and persistence risk. NOTE: A third-party states that this vulnerability should be rejected because the proof of concept does not demonstrate arbitrary code execution and fails to complete successfully.