Security readout for executives and security teams
Plain-English summary
OneFlow v0.9.0 has a denial-of-service flaw in floor division handling. If a workflow processes a crafted tensor containing zero as a divisor, the component can hit division by zero and stop service availability. The sources do not show data theft or integrity impact.
Executive priority
Treat as a moderate availability risk for AI or data-processing services using OneFlow v0.9.0. Prioritize internet-facing or customer-submitted tensor workflows first, then follow vendor guidance for remediation.
Technical view
The CVE describes a division-by-zero condition in OneFlow v0.9.0 flow.floor_divide(). The CVSS 3.1 score is 6.5 with network attack vector, low complexity, no privileges, user interaction required, and high availability impact only.
Likely exposure
Exposure is most likely where OneFlow v0.9.0 is used and accepts user-influenced tensors or model inputs that reach flow.floor_divide(). The source bundle does not provide CPEs or a broader affected-version range.
Exploitation context
The source bundle marks KEV as false and provides no evidence of active exploitation. CVSS indicates exploitation may be possible remotely without privileges but requires user interaction. Impact is limited to denial of service in the provided evidence.
Researcher notes
The CVE lists CWE-639, which does not clearly align with the described division-by-zero behavior. The bundle does not identify a patch, commit, workaround, or exact affected CPEs, so version validation and vendor tracking are important.
Mitigation direction
- Inventory applications and environments using OneFlow v0.9.0.
- Check the OneFlow issue and vendor repository for fixed release guidance.
- Validate or constrain tensor inputs before they reach floor_divide operations.
- Restrict untrusted access to services that process user-supplied tensors.
- Add defensive error handling around tensor execution paths.
Validation and detection
- Confirm whether deployed dependencies include OneFlow v0.9.0.
- Review code paths using flow.floor_divide with user-controlled divisors.
- Verify input validation rejects zero divisors before OneFlow execution.
- Check service logs for crashes tied to tensor division operations.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-639: 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.
Open ATT&CK lookupCVE-2025-65887 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H2.83.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Daisy2angCVE reference, mitre
- https://github.com/Oneflow-Inc/oneflowCVE reference, mitre
- https://github.com/Oneflow-Inc/oneflow/issues/10665CVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.