LiveActive security incident?Get immediate response
CVE Record

CVE-2025-71000: An issue in the flow.cuda.BoolTensor component of OneFlow v0.9.0 allows attackers to cause a Denial of Serv...

An issue in the flow.cuda.BoolTensor component of OneFlow v0.9.0 allows attackers to cause a Denial of Service (DoS) via a crafted input.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE describes a denial-of-service risk in OneFlow v0.9.0 involving the flow.cuda.BoolTensor component. A crafted input can make affected processing unavailable. The business impact is service disruption, not data theft or tampering, based on the provided sources.

Executive priority

Treat this as a high-priority availability risk where OneFlow v0.9.0 is deployed in production or exposed to untrusted inputs. Prioritize inventory first because the public affected-product metadata is incomplete.

Technical view

The CVE assigns CVSS 3.1 score 7.5 with network attack vector, low complexity, no privileges, and availability impact only. It is mapped to CWE-400, resource consumption. The affected metadata is incomplete, but the description names OneFlow v0.9.0 and flow.cuda.BoolTensor.

Likely exposure

Exposure is likely limited to environments running OneFlow v0.9.0, especially GPU-enabled services that process untrusted or remote-controlled inputs through flow.cuda.BoolTensor. The provided affected-product fields are n/a, so dependency inventory is necessary.

Exploitation context

The bundle says crafted input can trigger denial of service. It does not provide evidence of public exploitation, exploit maturity, or inclusion in CISA KEV. KEV is false in the supplied data.

Researcher notes

Key gaps are affected CPEs, fixed version, and detailed root cause. The CVSS vector indicates remote unauthenticated availability impact, but the provided sources do not substantiate active exploitation or disclose remediation details.

Mitigation direction

  • Identify any OneFlow v0.9.0 deployments or dependencies.
  • Review the OneFlow GitHub issue and vendor guidance for fixes.
  • Avoid passing untrusted input directly into affected tensor handling paths.
  • Apply resource limits and workload isolation around GPU-backed services.
  • Monitor affected services for crashes, hangs, or resource exhaustion.
  • Upgrade or patch when a vendor-supported fix is confirmed.

Validation and detection

  • Check SBOMs and lockfiles for OneFlow v0.9.0.
  • Map services using flow.cuda.BoolTensor or GPU tensor conversion.
  • Confirm whether those services accept remote or user-controlled input.
  • Run safe regression tests for input validation and failure handling.
  • Review logs for availability failures tied to tensor processing.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-400: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-71000 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2025-71000Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.