Quick answers
- Is CVE-2025-65891 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-65891 being exploited in the wild.
- How severe is CVE-2025-65891?
- High severity, with a CVSS score of 7.5, published 28 January 2026.
- Which products and versions are affected?
- Oneflow-Inc OneFlow 0.9.0.
- Is there a fix for CVE-2025-65891?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2025-65891 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-65891?
- Check whether you run Oneflow. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A denial-of-service vulnerability exists in OneFlow v0.9.0 due to improper validation of GPU device indices. The flaw is located in the flow.cuda.get_device_properties() function, which fails to sanitize the device_id input before passing it to the underlying CUDA API. Specifically, providing a negative or out-of-bounds integer causes a failed assertion in cudaSetDevice() within cuda_util.cpp, leading to a core dump and application crash. An attacker capable of influencing the device index parameter in a running OneFlow environment can trigger this crash without authentication. As of the advisory, the issue was identified in version 0.9.0.
Affected products
- Oneflow-Inc OneFlow 0.9.0
Timeline
- 2025-06-30: disclosed: Issue reported on GitHub repository
- 2026-01-28: advisory: CVE published to NVD