VulnerabilityPublished 28 Jan 2026Updated 29 Jan 2026

CVE-2025-71005: oneflow · CVE-2025-71005 is a medium-severity

Affects oneflowSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score

6.5Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 19% 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

Affected software

Product	Affected	Fixed in
GitHuboneflow-inc/oneflow`pkg:github/oneflow-inc/oneflow`Other threats	Affected =0.9.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Immediately restrict network exposure of OneFlow services, especially those using the oneflow.view component, to trusted internal users only.
Implement strict input validation and sanitization on all data fed into OneFlow tensor operations to prevent malformed or malicious inputs triggering floating point exceptions.
Monitor application logs and system metrics for signs of crashes or abnormal terminations related to tensor operations.
Employ runtime protections such as process isolation, resource limits, and watchdog timers to recover from unexpected crashes and maintain service availability.
Engage with OneFlow maintainers and security advisories to obtain patches or updates addressing this vulnerability as soon as they are released.
Consider deploying Web Application Firewalls (WAFs) or API gateways with custom rules to detect and block suspicious payloads targeting the vulnerable component.
Conduct internal security assessments and fuzz testing on OneFlow inputs to identify and remediate similar edge cases proactively.
Educate developers and data scientists on secure coding practices related to numerical computations and error handling in machine learning frameworks.

Description

CVE-2025-71005 is a medium-severity vulnerability in OneFlow v0.9.0, specifically in the oneflow.view component, where a floating point exception can be triggered by crafted input. This flaw allows unauthenticated attackers to cause a denial of service (DoS) condition, impacting availability without affecting confidentiality or integrity. Exploitation requires user interaction but no privileges, and no known exploits are currently in the wild. The vulnerability stems from improper handling of floating point operations leading to exceptions that crash or hang the application. European organizations using OneFlow for machine learning or data processing may face service disruptions if targeted. Mitigation involves input validation and patching once updates become available, as no official patch links are currently provided. Countries with significant AI and tech sectors, such as Germany, France, and the UK, are most likely to be affected due to higher adoption of such frameworks.

Impact

For European organizations leveraging OneFlow in AI, machine learning, or data processing pipelines, this vulnerability poses a risk of service outages due to denial of service attacks. Such disruptions could affect critical business operations, research activities, or cloud services relying on OneFlow, leading to productivity loss and potential financial impact. Although confidentiality and integrity are not directly compromised, availability degradation can indirectly affect trust and operational continuity. Organizations with public-facing APIs or services that process untrusted input using OneFlow are at higher risk. The medium severity indicates that while exploitation is feasible without privileges, it requires user interaction, somewhat limiting widespread automated attacks. However, targeted attacks against AI infrastructure in sectors like finance, healthcare, or manufacturing could cause significant operational interruptions. The lack of patches and known exploits means organizations must proactively implement mitigations to reduce exposure. Overall, the impact is primarily operational but could escalate if combined with other vulnerabilities or used as a distraction in multi-vector attacks.

Summary

CVE-2025-71005 identifies a floating point exception vulnerability in the oneflow.view component of OneFlow version 0.9.0. OneFlow is a machine learning framework used for efficient tensor computations and model training. The vulnerability arises from improper handling of floating point operations within the view component, which processes tensor reshaping and viewing operations. When an attacker supplies specially crafted input data that triggers this floating point exception (CWE-369), it causes the application to crash or become unresponsive, resulting in a denial of service (DoS) condition. The CVSS 3.1 score of 6.5 reflects a medium severity, with an attack vector of network (AV:N), low attack complexity (AC:L), no privileges required (PR:N), but requiring user interaction (UI:R). The scope remains unchanged (S:U), and the impact affects availability only (A:H), with no confidentiality or integrity impact. No known exploits have been reported in the wild, and no patches have been officially released yet. This vulnerability could be exploited remotely by sending malicious input to exposed OneFlow services or APIs that utilize the vulnerable component. The floating point exception likely results from edge cases in tensor dimension calculations or memory access during the view operation. This vulnerability highlights the importance of robust input validation and error handling in numerical computing frameworks to prevent service disruptions.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

WeaknessesCWE-369

Technical details

References

Community reviews

Related threats