CVE-2021-41195

CVE-2021-41195 is a medium-severity integer overflow or wraparound vulnerability in tensorflow (pip), affecting versions >= 2.6.0, < 2.6.1. It is fixed in 2.6.1, 2.5.2, 2.4.4.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Crash in tf.math.segment_* operations

For more information

Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.

Attribution

This vulnerability has been reported externally via a GitHub issue.

Impact

The implementation of tf.math.segment_* operations results in a CHECK-fail related abort (and denial of service) if a segment id in segment_ids is large.

import tensorflow as tf

tf.math.segment_max(data=np.ones((1,10,1)), segment_ids=[1676240524292489355])
tf.math.segment_min(data=np.ones((1,10,1)), segment_ids=[1676240524292489355])
tf.math.segment_mean(data=np.ones((1,10,1)), segment_ids=[1676240524292489355])    
tf.math.segment_sum(data=np.ones((1,10,1)), segment_ids=[1676240524292489355])
tf.math.segment_prod(data=np.ones((1,10,1)), segment_ids=[1676240524292489355])

This is similar to CVE-2021-29584 (and similar other reported vulnerabilities in TensorFlow, localized to specific APIs): the implementation (both on CPU and GPU) computes the output shape using AddDim. However, if the number of elements in the tensor overflows an int64_t value, AddDim results in a CHECK failure which provokes a std::abort. Instead, code should use AddDimWithStatus.

An arithmetic operation produces a value that exceeds the integer type's maximum, causing it to wrap to an unexpected small value. Typical impact: incorrect size calculations leading to heap overflows or logic errors.

CVE-2021-41195 has a CVSS score of 5.5 (Medium). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.6.1, 2.5.2, 2.4.4); upgrading removes the vulnerable code path.

Affected versions

tensorflow (>= 2.6.0, < 2.6.1) tensorflow (>= 2.5.0, < 2.5.2) tensorflow (< 2.4.4) tensorflow-cpu (>= 2.6.0, < 2.6.1) tensorflow-cpu (>= 2.5.0, < 2.5.2) tensorflow-cpu (< 2.4.4) tensorflow-gpu (>= 2.6.0, < 2.6.1) tensorflow-gpu (>= 2.5.0, < 2.5.2) tensorflow-gpu (< 2.4.4)

Security releases

tensorflow → 2.6.1 (pip) tensorflow → 2.5.2 (pip) tensorflow → 2.4.4 (pip) tensorflow-cpu → 2.6.1 (pip) tensorflow-cpu → 2.5.2 (pip) tensorflow-cpu → 2.4.4 (pip) tensorflow-gpu → 2.6.1 (pip) tensorflow-gpu → 2.5.2 (pip) tensorflow-gpu → 2.4.4 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

We have patched the issue in GitHub commit e9c81c1e1a9cd8dd31f4e83676cab61b60658429 (merging #51733).

The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.

Frequently Asked Questions

  1. What is CVE-2021-41195? CVE-2021-41195 is a medium-severity integer overflow or wraparound vulnerability in tensorflow (pip), affecting versions >= 2.6.0, < 2.6.1. It is fixed in 2.6.1, 2.5.2, 2.4.4. An arithmetic operation produces a value that exceeds the integer type's maximum, causing it to wrap to an unexpected small value.
  2. How severe is CVE-2021-41195? CVE-2021-41195 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which packages are affected by CVE-2021-41195?
    • tensorflow (pip) (versions >= 2.6.0, < 2.6.1)
    • tensorflow-cpu (pip) (versions >= 2.6.0, < 2.6.1)
    • tensorflow-gpu (pip) (versions >= 2.6.0, < 2.6.1)
  4. Is there a fix for CVE-2021-41195? Yes. CVE-2021-41195 is fixed in 2.6.1, 2.5.2, 2.4.4. Upgrade to this version or later.
  5. Is CVE-2021-41195 exploitable, and should I be worried? Whether CVE-2021-41195 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2021-41195 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2021-41195?
    • Upgrade tensorflow to 2.6.1 or later
    • Upgrade tensorflow to 2.5.2 or later
    • Upgrade tensorflow to 2.4.4 or later
    • Upgrade tensorflow-cpu to 2.6.1 or later
    • Upgrade tensorflow-cpu to 2.5.2 or later
    • Upgrade tensorflow-cpu to 2.4.4 or later
    • Upgrade tensorflow-gpu to 2.6.1 or later
    • Upgrade tensorflow-gpu to 2.5.2 or later
    • Upgrade tensorflow-gpu to 2.4.4 or later

Other vulnerabilities in tensorflow

Stop the waste.
Protect your environment with Kodem.