PatchSiren

PatchSiren cyber security CVE debrief

CVE-2025-65891 Oneflow Inc CVE debrief

CVE-2025-65891 is a high-severity vulnerability in OneFlow v0.9.0, allowing attackers to trigger a Denial of Service (DoS) by invoking flow.cuda.get_device_properties() with an invalid or negative device index. The CVE record was published on 2026-01-28T18:16:50.067Z and has not been modified since then. The NVD entry is currently modified. This vulnerability has significant implications for users of OneFlow v0.9.0, as it can be exploited to cause a Denial of Service. The exposure question revolves around whether affected product deployments exist in managed environments. The likely defender workflow involves verifying affected systems, applying patches, and implementing compensating controls.

Vendor
Oneflow Inc
Product
Oneflow
CVSS
HIGH 7.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-01-28
Original CVE updated
2026-07-05
Advisory published
2026-01-28
Advisory updated
2026-07-05

Who should care

Users of OneFlow v0.9.0, particularly those with deployments in managed environments, should be aware of this high-severity vulnerability and take necessary precautions to prevent exploitation. This includes operators, platform administrators, vulnerability management teams, and security teams who need to assess the impact and implement mitigations.

Technical summary

A GPU device-ID validation flaw in OneFlow v0.9.0 allows attackers to trigger a Denial of Service (DoS) by invoking flow.cuda.get_device_properties() with an invalid or negative device index. This vulnerability has a CVSS score of 7.5 and is classified as HIGH. The vulnerability exists due to inadequate validation of GPU device IDs, which could lead to a denial of service. Users should verify their systems and apply patches if available.

Defensive priority

High priority should be given to patching or mitigating this vulnerability, as it can be exploited to cause a Denial of Service. The priority posture is high due to the potential for significant disruption.

Recommended defensive actions

  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The CVE record and NVD entry provide limited information about this vulnerability. Further investigation and testing may be necessary to fully understand the impact and potential mitigations. The source details are limited, and defenders should verify the affected scope and vendor guidance. The NVD entry and CVE record are the primary sources of information for this vulnerability.

Official resources

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-01-28T18:16:50.067Z and has not been modified since then.