VulnerabilityPublished 28 Jan 2026Updated 29 Jan 2026

CVE-2025-71002: OneFlow · CVE-2025-71002 is a medium-severity

Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Given the lack of an official patch, European organizations should implement strict input validation and sanitization to prevent malformed data from reaching the flow.column_stack component. Network-level protections such as firewalls and intrusion detection systems should be configured to monitor and block suspicious traffic patterns targeting OneFlow services. Restrict access to OneFlow instances to trusted users and networks, minimizing exposure to untrusted inputs. Employ application-layer gateways or proxies to inspect and filter data before processing. Monitor logs and system behavior for signs of crashes or anomalies indicative of exploitation attempts. Consider isolating OneFlow workloads in containerized or sandboxed environments to limit impact of potential crashes. Engage with OneFlow maintainers and subscribe to security advisories for timely patch releases. Finally, develop incident response plans to quickly address DoS events affecting AI services.

Description

CVE-2025-71002 is a medium-severity vulnerability in OneFlow v0.9.0's flow.column_stack component, where a crafted input triggers a floating-point exception causing a denial of service (DoS). The vulnerability requires no privileges but does require user interaction and can be exploited remotely over the network. It impacts availability without affecting confidentiality or integrity. No known exploits are currently in the wild, and no patches have been published yet. European organizations using OneFlow for machine learning or data processing may experience service disruptions if targeted. Mitigation involves input validation, restricting access to vulnerable components, and monitoring for anomalous inputs. Countries with strong AI and data science sectors, such as Germany, France, and the UK, are more likely to be affected.

Impact

For European organizations, the primary impact is service disruption due to denial of service attacks targeting OneFlow deployments. This can affect availability of AI and data processing services, potentially delaying critical business operations, research, or analytics. Organizations relying on OneFlow in production environments, especially in sectors like finance, healthcare, and manufacturing where AI workloads are common, may face operational downtime. While confidentiality and integrity are not directly impacted, the loss of availability could indirectly affect business continuity and trust. The absence of patches increases risk exposure until mitigations are applied. Additionally, if attackers leverage this vulnerability in combination with other threats, it could facilitate more complex attack chains. The impact is more pronounced in organizations with externally facing AI services or those processing untrusted inputs without adequate filtering.

Summary

CVE-2025-71002 is a vulnerability identified in the flow.column_stack component of OneFlow version 0.9.0, a machine learning framework. The flaw is a floating-point exception (FPE) triggered by specially crafted inputs. This exception leads to a denial of service (DoS) condition, causing the affected process or service to crash or become unresponsive. The vulnerability is remotely exploitable over the network without requiring any privileges, but it does require user interaction, such as processing maliciously crafted data inputs. The CVSS v3.1 base score is 6.5, indicating medium severity, with the vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H, meaning no impact on confidentiality or integrity but a high impact on availability. The underlying weaknesses correspond to CWE-369 (Divide by Zero), CWE-704 (Incorrect Type Conversion or Cast), and CWE-681 (Incorrect Conversion between Numeric Types). No patches or fixes have been released at the time of publication, and no known exploits have been observed in the wild. The vulnerability could disrupt services relying on OneFlow for data stacking operations, potentially affecting AI workflows and data pipelines.

CWE-369Divide By Zero (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product divides a value by zero.
OWASP Cheat Sheets
Logging (opens in a new tab)
Error Handling (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-704Incorrect Type Conversion or Cast (opens in a new tab)
Class weakness
The product does not correctly convert an object, resource, or structure from one type to a different type.
CWE-681Incorrect Conversion between Numeric Types (opens in a new tab)
Base weaknessLikelihood of exploit: High
When converting from one data type to another, such as long to integer, data can be omitted or translated in a way that produces unexpected values. If the resulting values are used in a sensitive context, then dangerous behaviors may occur.
Implementation
Avoid making conversion between numeric types. Always check for the allowed ranges.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 5 Feb 2026, 08:49 UTC

WeaknessesCWE-369, CWE-704, CWE-681

Technical details

References

Community reviews

Related threats