CVE-2025-65888: A dimension validation flaw in the flow.empty() component of OneFlow 0.9.0 allows attackers to cause a Deni...
A dimension validation flaw in the flow.empty() component of OneFlow 0.9.0 allows attackers to cause a Denial of Service (DoS) via a negative or excessively large dimension value.
Security readout for executives and security teams
Plain-English summary
CVE-2025-65888 is a denial-of-service flaw in OneFlow 0.9.0. If an attacker can influence dimensions passed to flow.empty(), negative or extremely large values may crash or exhaust resources. The impact is availability, not data theft or modification, based on the provided CVSS vector.
Executive priority
Treat this as a high-priority availability risk for services using OneFlow 0.9.0 with attacker-controlled dimensions. It is less urgent for isolated research environments without untrusted input paths.
Technical view
The CVE describes improper dimension validation in OneFlow's flow.empty() component. It is mapped to CWE-400 and scored CVSS 3.1 7.5 with network, low-complexity, unauthenticated, no-user-interaction conditions and high availability impact only.
Likely exposure
Exposure is most likely where OneFlow 0.9.0 is deployed and untrusted or loosely validated input can reach tensor-shape or dimension parameters. The CVE affected-product metadata is incomplete, listing vendor/product as n/a, so confirm actual dependency versions locally.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. The described attack condition is resource exhaustion through invalid dimensions, but the bundle does not provide public evidence of exploitation in the wild.
Researcher notes
The record is sparse: affected CPEs are absent and no patch is named in the provided bundle. Analysis should anchor on OneFlow 0.9.0, flow.empty(), CWE-400, and the GitHub issue until vendor details are clearer.
Mitigation direction
Inventory systems and applications using OneFlow, especially version 0.9.0.
Check OneFlow vendor guidance and issue 10664 for fixed versions or workarounds.
Validate and bound all user-controlled tensor dimensions before calling flow.empty().
Limit service resource usage to reduce blast radius from allocation failures.
Prioritize internet-facing or multi-tenant ML services first.
Validation and detection
Confirm installed OneFlow versions in runtime images, notebooks, and dependency lockfiles.
Review code paths where external input influences tensor dimensions.
Check monitoring for crashes, memory exhaustion, or repeated allocation failures.
Verify input validation rejects negative and excessive dimensions before OneFlow calls.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.