PatchSiren cyber security CVE debrief
CVE-2025-65889 Oneflow-Inc CVE debrief
CVE-2025-65889 is a type validation flaw in OneFlow v0.9.0's flow.dstack() component, allowing attackers to cause a Denial of Service (DoS) via crafted input. The CVE record was published on 2026-01-28T17:16:08.560Z. This vulnerability has a CVSS score of 7.5 and is classified as HIGH severity. Users of OneFlow v0.9.0 should be aware of this vulnerability and take necessary precautions. The debrief is based on the supplied source corpus and CVE record.
- 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 responsible for system administration, security, and vulnerability management, should be aware of this vulnerability. They should assess their exposure, review vendor guidance, and apply patches or mitigations as available. Security teams should prioritize this vulnerability for remediation due to its potential impact on system availability.
Technical summary
A type validation flaw in the flow.dstack() component of OneFlow v0.9.0 allows attackers to cause a Denial of Service (DoS) via a crafted input. The vulnerability has a CVSS score of 7.5 and is classified as HIGH severity. This issue arises from inadequate input validation, which could lead to system crashes or instability. Users should review their OneFlow installations for potential exposure and apply patches or mitigations as available.
Defensive priority
High priority should be given to patching or mitigating this vulnerability to prevent potential Denial of Service attacks. Defenders should focus on verifying OneFlow v0.9.0 installations, applying vendor patches, and implementing compensating controls to detect and prevent potential attacks.
Recommended defensive actions
- Inventory and verify OneFlow v0.9.0 installations
- Apply vendor patches or updates if available
- Implement compensating controls to detect and prevent potential attacks
- Monitor for suspicious activity and exception tracking
- 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
Evidence notes
The CVE record and NVD detail provide information on the vulnerability, but further investigation is needed to determine the full scope of affected systems and potential impact. The evidence is limited to public sources, and defenders should verify the vulnerability's presence in their environments. Additional details may be necessary to fully understand the vulnerability's effects and to plan appropriate mitigations.
Sources and references
Verified primary and authoritative sources
-
CVE-2025-65889 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2025-65889
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2025-65889 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2025-65889
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/Daisy2ang
[email protected] - Not Applicable
-
Source reference
Unverified legacy reference
URL: https://github.com/Oneflow-Inc/oneflow
[email protected] - Product
-
Mitigation or vendor reference
Unverified legacy reference
URL: https://github.com/Oneflow-Inc/oneflow/issues/10663
[email protected] - Exploit, Issue Tracking, Vendor Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.