Quick answers
- Is CVE-2025-65890 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-65890 being exploited in the wild.
- How severe is CVE-2025-65890?
- 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-65890?
- 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-65890 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-65890?
- 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 device-ID validation flaw exists in OneFlow v0.9.0 within the CUDA synchronization logic. The vulnerability is triggered when the `flow.cuda.synchronize()` function is called with an invalid or out-of-range GPU device index. Internally, the framework fails to validate the index before passing it to `cudaSetDevice()`. When the underlying CUDA call fails, the application triggers a `Check failure` via Google Logging (glog), leading to an immediate abort and core dump. An attacker capable of influencing the device index parameter can remotely or locally cause the deep learning process to terminate unexpectedly.
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