Security readout for executives and security teams
Plain-English summary
This CVE describes a denial-of-service risk in OneFlow v0.9.0. A malformed GPU device ID passed to flow.cuda.get_device_capability() can crash or disrupt availability. The public metadata rates it high because it is network-reachable, low-complexity, unauthenticated, and affects availability only.
Executive priority
Treat this as a high-priority availability risk if OneFlow v0.9.0 supports production GPU workloads. Prioritize inventory and vendor guidance review before emergency action, because the public record does not confirm exploitation or name a patch.
Technical view
The issue is a GPU device-ID validation flaw in OneFlow v0.9.0, mapped to CWE-400. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Public affected-product metadata is incomplete, but the description names OneFlow v0.9.0 and the flow.cuda.get_device_capability() component.
Likely exposure
Exposure is most likely where OneFlow v0.9.0 is deployed in GPU-enabled services and untrusted input can influence GPU device selection or capability checks. The bundle does not identify CPEs, distributions, downstream packages, or hosted service exposure.
Exploitation context
The source bundle does not show CISA KEV listing or public active exploitation evidence. It describes a crafted device ID causing denial of service, but does not provide confirmed exploit activity, patch status, or affected deployment patterns.
Researcher notes
Evidence is limited. The CVE record provides severity, vector, CWE-400, and the vulnerable component, but affected-product metadata is n/a and no official fix is named in the bundle. Avoid assuming broader OneFlow versions are affected without vendor confirmation.
Mitigation direction
- Inventory OneFlow usage, especially version 0.9.0 in GPU-enabled environments.
- Check OneFlow project guidance and the linked issue for fixed versions or workarounds.
- Restrict untrusted users from controlling GPU device IDs or capability-check inputs.
- Reduce network exposure of services that route requests into OneFlow GPU capability calls.
- Monitor vendor and CVE records for patch or advisory updates.
Validation and detection
- Search dependency manifests, lockfiles, containers, and notebooks for OneFlow v0.9.0.
- Identify code paths calling flow.cuda.get_device_capability().
- Confirm whether external requests can influence the device ID passed to that function.
- Review service logs for unexplained crashes or availability failures around GPU capability checks.
- Track the linked OneFlow issue for reproduction details and remediation status.
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-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.
Open ATT&CK lookupCVE-2025-70999 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
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:N/S:U/C:N/I:N/A:H3.93.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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/oneflow/issues/10660CVE 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.
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.