<?xml version="1.0" encoding="utf-8"?>
  <?xml-stylesheet type="text/xsl" href="sa-render.xsl"?>
  <update from="huaweicloud.com" type="security" status="stable" version="1">
    <id>HCE2-SA-2026-0092</id>
    <title>An update for python-ply is now available for HCE 2.0</title>
    <severity>Critical</severity>
    <release>HCE 2.0</release>
    <issued date="2026-03-23 23:18:33"/>
    <updated date="2026-03-23 23:18:33"/>
    <references>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2025-56005" id="CVE-2025-56005" title="CVE-2025-56005 Base Score: 9.8 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H" type="cve"/>
    </references>
    <description>Security Fix(es):

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. (CVE-2025-56005)
</description>
    <pkglist>
      <collection short="HCE 2.0" package="python-ply">
        <name>HCE 2.0</name>
        <package arch="noarch" name="python3-ply" version="3.11" release="2.r1.hce2">
          <filename>python3-ply-3.11-2.r1.hce2.noarch.rpm</filename>
        </package>
        <package arch="noarch" name="python-ply-help" version="3.11" release="2.r1.hce2">
          <filename>python-ply-help-3.11-2.r1.hce2.noarch.rpm</filename>
        </package>
      </collection>
    </pkglist>
  </update>
