Security readout for executives and security teams
Plain-English summary
CVE-2025-65886 is a high-severity availability issue in OneFlow v0.9.0. Crafted tensor shapes can trigger a shape mismatch that may crash or exhaust processing, causing denial of service. The public bundle does not identify data theft, privilege escalation, a confirmed patch, or active exploitation.
Executive priority
Treat this as a high-priority availability risk for any business service depending on OneFlow v0.9.0 with untrusted inputs. Prioritize inventory, exposure reduction, and vendor guidance tracking before assuming a patch or workaround exists.
Technical view
The CVE describes CWE-400 resource consumption from malformed tensor shape handling in OneFlow v0.9.0. CVSS 3.1 is 7.5 with network attack vector, low complexity, no privileges, no user interaction, unchanged scope, and high availability impact only. Affected metadata is sparse despite the description naming OneFlow v0.9.0.
Likely exposure
Exposure is most likely where OneFlow v0.9.0 is used in network-reachable ML services, inference APIs, notebooks, or batch systems that process untrusted tensor shapes. The CVE affected-product fields are incomplete, so teams should verify actual OneFlow usage rather than rely only on CPE data.
Exploitation context
The source bundle does not show CISA KEV listing or other evidence of active exploitation. The CVSS vector indicates remote, unauthenticated, low-complexity denial-of-service potential, but public details in the bundle are limited to crafted tensor shapes and the linked GitHub issue.
Researcher notes
Key gaps are incomplete affected-product metadata and no named fix in the provided sources. Analysis should focus on confirming OneFlow v0.9.0 usage, whether shape inputs cross trust boundaries, and whether issue 10666 contains vendor-confirmed remediation details.
Mitigation direction
Identify deployments using OneFlow v0.9.0 or dependencies that bundle it.
Review the upstream issue and CVE record for vendor remediation guidance.
Restrict untrusted tensor shape input at service boundaries where feasible.
Run ML workloads with resource limits and restart isolation for availability.
Plan upgrade or workaround only when confirmed by OneFlow guidance.
Validation and detection
Confirm OneFlow versions in ML services, notebooks, inference APIs, and batch jobs.
Map endpoints or jobs that accept user-controlled model or tensor inputs.
Check logs for crashes, worker restarts, or resource exhaustion around tensor parsing.
Track GitHub issue 10666 and CVE updates for remediation status.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-400 · source CWE mapping
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.