CVE-2021-41218Public exploit

Process crash via unchecked zero split count

Published Nov 5, 2021 · Updated Aug 4, 2024

Divide-by-zero in TensorFlow before 2.4.4, 2.5.0 through 2.5.1, and 2.6.0 allows local users to crash a consuming process. The AllToAll shape function reads split_count without enforcing a positive value, then divides each known split dimension by that value. The trigger requires local ability to build and execute a TensorFlow graph; the reported consequence is termination of that process, with no data disclosure or modification.

CVSS severity5.5
Medium
EPSS probability0.13%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Divide-by-zero in TensorFlow before 2.4.4, 2.5.0 through 2.5.1, and 2.6.0 allows local users to crash a consuming process. The AllToAll shape function reads split_count without enforcing a positive value, then divides each known split dimension by that value. The trigger requires local ability to build and execute a TensorFlow graph; the reported consequence is termination of that process, with no data disclosure or modification.

The record

CVE
CVE-2021-41218
Published
Nov 5, 2021
Updated
Aug 4, 2024
Vendor
Google
Product
TensorFlow
Classifications
CWE-369
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Nov 5, 2021CVE publishedPublication date reported by the CVE source.
  2. Aug 4, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 2.4.4
  2. Affected versionversion=>= 2.5.0, < 2.5.2
  3. Affected versionversion=>= 2.6.0, < 2.6.1

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Google · TensorFlowversion=< 2.4.4; version=>= 2.5.0, < 2.5.2; version=>= 2.6.0, < 2.6.1

Published CVSS scores

2.1NIST NVDAV:L/AC:L/Au:N/C:N/I:N/A:P
5.5GitHub, Inc.CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-369Divide By Zero

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo