Quick answers
- Is CVE-2025-63397 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-63397 being exploited in the wild.
- How severe is CVE-2025-63397?
- Medium severity, with a CVSS score of 6.5, published 10 November 2025.
- Which products and versions are affected?
- Oneflow-Inc OneFlow 0.9.0.
- Is there a fix for CVE-2025-63397?
- 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-63397 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-63397?
- 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 vulnerability exists in OneFlow v0.9.0 due to improper input validation during tensor broadcasting and type conversion. Specifically, when performing operations such as adding a Python list (sequence) to a tensor generated by 'flow.eye', the system fails to properly validate dimension and shape consistency between the Python object and the native C++ backend. This leads to a segmentation fault and subsequent core dump. An attacker can exploit this by providing malformed input sequences to affected API endpoints, resulting in a denial-of-service (DoS). A patch has been identified in the project's issue tracking system.
Affected products
- Oneflow-Inc OneFlow 0.9.0
Timeline
- 2025-06-30: disclosed: Issue reported on GitHub repository
- 2025-11-10: advisory: CVE published