What is CVE-2022-36016?

CVE-2022-36016 is a low-severity security vulnerability in tensorflow (pip), affecting versions < 2.7.2. It is fixed in 2.7.2, 2.8.1, 2.9.1.

Which packages are affected by CVE-2022-36016?

tensorflow (pip) versions < 2.7.2; tensorflow-cpu (pip) versions < 2.7.2; tensorflow-gpu (pip) versions < 2.7.2.

Is there a fix for CVE-2022-36016?

Yes. CVE-2022-36016 is fixed in 2.7.2, 2.8.1, 2.9.1. Upgrade to this version or later.

Is CVE-2022-36016 exploitable, and should I be worried?

Whether CVE-2022-36016 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.

What actually determines whether CVE-2022-36016 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.

How do I fix CVE-2022-36016?

Upgrade: tensorflow to 2.7.2 or later, tensorflow to 2.8.1 or later, tensorflow to 2.9.1 or later, tensorflow-cpu to 2.7.2 or later, tensorflow-cpu to 2.8.1 or later, tensorflow-cpu to 2.9.1 or later, tensorflow-gpu to 2.7.2 or later, tensorflow-gpu to 2.8.1 or later, tensorflow-gpu to 2.9.1 or later.

CVE-2022-36016 in tensorflow

Q: Which packages are affected by CVE-2022-36016?

tensorflow (pip) versions < 2.7.2; tensorflow-cpu (pip) versions < 2.7.2; tensorflow-gpu (pip) versions < 2.7.2.

Q: Is there a fix for CVE-2022-36016?

Yes. CVE-2022-36016 is fixed in 2.7.2, 2.8.1, 2.9.1. Upgrade to this version or later.

Q: Is CVE-2022-36016 exploitable, and should I be worried?

Whether CVE-2022-36016 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.

Q: What actually determines whether CVE-2022-36016 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.

Q: How do I fix CVE-2022-36016?

Upgrade: tensorflow to 2.7.2 or later, tensorflow to 2.8.1 or later, tensorflow to 2.9.1 or later, tensorflow-cpu to 2.7.2 or later, tensorflow-cpu to 2.8.1 or later, tensorflow-cpu to 2.9.1 or later, tensorflow-gpu to 2.7.2 or later, tensorflow-gpu to 2.8.1 or later, tensorflow-gpu to 2.9.1 or later.

Summary

TensorFlow vulnerable to CHECK-fail in tensorflow::full_type::SubstituteFromAttrs

For more information

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

Impact

When tensorflow::full_type::SubstituteFromAttrs receives a FullTypeDef& t that is not exactly three args, it triggers a CHECK-fail instead of returning a status.

Status SubstituteForEach(AttrMap& attrs, FullTypeDef& t) {
  DCHECK_EQ(t.args_size(), 3);

  const auto& cont = t.args(0);
  const auto& tmpl = t.args(1);
  const auto& t_var = t.args(2);

Affected versions

tensorflow (< 2.7.2) tensorflow (>= 2.8.0, < 2.8.1) tensorflow (>= 2.9.0, < 2.9.1) tensorflow-cpu (< 2.7.2) tensorflow-cpu (>= 2.8.0, < 2.8.1) tensorflow-cpu (>= 2.9.0, < 2.9.1) tensorflow-gpu (< 2.7.2) tensorflow-gpu (>= 2.8.0, < 2.8.1) tensorflow-gpu (>= 2.9.0, < 2.9.1)

Security releases

tensorflow → 2.7.2 (pip) tensorflow → 2.8.1 (pip) tensorflow → 2.9.1 (pip) tensorflow-cpu → 2.7.2 (pip) tensorflow-cpu → 2.8.1 (pip) tensorflow-cpu → 2.9.1 (pip) tensorflow-gpu → 2.7.2 (pip) tensorflow-gpu → 2.8.1 (pip) tensorflow-gpu → 2.9.1 (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 environment New to Kodem? Get a demo →

Remediation advice

We have patched the issue in GitHub commit 6104f0d4091c260ce9352f9155f7e9b725eab012.
The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range.

Frequently Asked Questions

What is CVE-2022-36016? CVE-2022-36016 is a low-severity security vulnerability in tensorflow (pip), affecting versions < 2.7.2. It is fixed in 2.7.2, 2.8.1, 2.9.1.
Which packages are affected by CVE-2022-36016?
- tensorflow (pip) (versions < 2.7.2)
- tensorflow-cpu (pip) (versions < 2.7.2)
- tensorflow-gpu (pip) (versions < 2.7.2)
Is there a fix for CVE-2022-36016? Yes. CVE-2022-36016 is fixed in 2.7.2, 2.8.1, 2.9.1. Upgrade to this version or later.
Is CVE-2022-36016 exploitable, and should I be worried? Whether CVE-2022-36016 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
What actually determines whether CVE-2022-36016 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.
How do I fix CVE-2022-36016?
- Upgrade tensorflow to 2.7.2 or later
- Upgrade tensorflow to 2.8.1 or later
- Upgrade tensorflow to 2.9.1 or later
- Upgrade tensorflow-cpu to 2.7.2 or later
- Upgrade tensorflow-cpu to 2.8.1 or later
- Upgrade tensorflow-cpu to 2.9.1 or later
- Upgrade tensorflow-gpu to 2.7.2 or later
- Upgrade tensorflow-gpu to 2.8.1 or later
- Upgrade tensorflow-gpu to 2.9.1 or later

Other vulnerabilities in tensorflow

CVE-IDSeverityPackage summary

CVE-2023-33976Hightensorflow: TensorFlow has segfault in array_ops.upper_bound CVE-2023-25661Mediumtensorflow: TensorFlow Denial of Service vulnerability CVE-2023-25659Hightensorflow: TensorFlow vulnerable to Out-of-Bounds Read in DynamicStitch CVE-2023-25660Hightensorflow: TensorFlow vulnerable to seg fault in `tf.raw_ops.Print`CVE-2023-25662Hightensorflow: TensorFlow vulnerable to integer overflow in EditDistance