CVE-2025-71008VulnerabilityPublished 29 Jan 2026

CVE-2025-71008: oneflow · n/a

Affects oneflowSource CVE Database V5

Not known to be exploited · CVSS 6.2 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.2Medium

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

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

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

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

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
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: None: The vulnerable system can be exploited without any interaction from any user.
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 29 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 2026-10-26.

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 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
PyPIoneflow`pkg:pypi/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

To mitigate CVE-2025-71008, European organizations should first identify all instances of OneFlow v0.9.0 in their environments, especially those exposed to external or untrusted inputs. Until a patch is available, implement strict input validation and sanitization to prevent malformed or malicious data from reaching the vulnerable function. Employ sandboxing or containerization to isolate OneFlow processes, limiting the blast radius of potential crashes. Monitor application logs and system metrics for signs of segmentation faults or abnormal terminations related to OneFlow components. Consider implementing redundancy and failover mechanisms in AI/ML pipelines to maintain availability during potential DoS events. Engage with OneFlow maintainers or community to track patch releases and apply updates promptly once available. Additionally, restrict network access to OneFlow services to trusted users and systems only, minimizing exposure. For critical systems, evaluate fallback options or alternative frameworks until the vulnerability is resolved.

Description

A segmentation violation in the oneflow._oneflow_internal.autograd.Function.FunctionCtx.mark_non_differentiable component of OneFlow v0.9.0 allows attackers to cause a Denial of Service (DoS) via a crafted input.

Impact

For European organizations, the primary impact of CVE-2025-71008 is the potential disruption of AI and machine learning workflows that utilize OneFlow v0.9.0. This could affect research institutions, technology companies, and industries relying on AI-driven analytics or automation, leading to downtime and productivity loss. In sectors such as automotive, finance, healthcare, and manufacturing—where AI models are increasingly integrated—service interruptions could delay critical decision-making or operational processes. Since the vulnerability causes a DoS via segmentation faults, it could be exploited to crash services repeatedly, potentially leading to denial of access for legitimate users. Although no data breach or code execution is indicated, the availability impact alone could have significant operational consequences. Organizations with exposed OneFlow APIs or those processing untrusted inputs are at higher risk. Additionally, the absence of a patch means organizations must rely on mitigations until an official fix is released. The impact is more pronounced in environments where OneFlow is part of production pipelines rather than isolated development setups.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Jan 2026, 15:27 UTC

Technical details

References

Community reviews

Related threats