Quick answers
- Is CVE-2022-46741 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2022-46741 being exploited in the wild.
- How severe is CVE-2022-46741?
- Low severity, with a CVSS score of 3.1, published 29 June 2026.
- Which products and versions are affected?
- PaddlePaddle Paddle before 2.4; paddlepaddle (PyPI) ECOSYSTEM:introduced=0,fixed=2.4.
- Is there a fix for CVE-2022-46741?
- Yes. paddlepaddle (PyPI): upgrade to 2.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2022-46741 attacked?
- It is attacked over the network.
- Am I affected by CVE-2022-46741?
- Check whether you run PaddlePaddle Paddle or paddlepaddle (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- paddlepaddle (PyPI): upgrade to 2.4 or later
pip install "paddlepaddle>=2.4"
Technical details
An out-of-bounds read vulnerability (CWE-125) exists in the gather_tree function in PaddlePaddle versions prior to 2.4. The vulnerability can be triggered by sending specially crafted input to the affected function without requiring authentication or user interaction, since PaddlePaddle is typically used as a library or service. An attacker can read beyond allocated memory boundaries, potentially disclosing sensitive information from the process memory. The vulnerability was patched in version 2.4, with fixes available in pull request #47051 and subsequent commits that add input validation and error handling.
Affected products
- PaddlePaddle Paddle before 2.4
Identifiers
- CVE-2022-46741
- GHSA-2hvc-hwg3-hpvw
- PYSEC-2026-441
Timeline
- 2022-12-07: disclosed
- 2022-10-18: patched: Fix available in PR #47051 merged to develop branch