Runtime crash via unchecked empty topk tensor
Published Jan 3, 2024 · Updated Jun 3, 2025
Divide-by-zero in PaddlePaddle before 2.6.0 allows context-dependent attackers to crash the runtime through crafted paddle.topk inputs. The CPU TopkKernel accepts an empty x tensor with k set to one and proceeds without verifying that x.numel() is at least k. An application must pass attacker-influenced tensor shapes to paddle.topk, and triggering the flaw terminates the hosting runtime rather than exposing or altering data.
Summary
What happened
Divide-by-zero in PaddlePaddle before 2.6.0 allows context-dependent attackers to crash the runtime through crafted paddle.topk inputs. The CPU TopkKernel accepts an empty x tensor with k set to one and proceeds without verifying that x.numel() is at least k. An application must pass attacker-influenced tensor shapes to paddle.topk, and triggering the flaw terminates the hosting runtime rather than exposing or altering data.
The record
- CVE
- CVE-2023-52305
- Published
- Jan 3, 2024
- Updated
- Jun 3, 2025
- Vendor
- PaddlePaddle
- Product
- PaddlePaddle
- Classifications
- CWE-369, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 3, 2024CVE publishedPublication date reported by the CVE source.
- Jun 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.6.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo