CVE-2022-41883: PYSEC-2026-3376 - Out of bounds segmentation fault due to unequal op inputs in Tensorflow

Quick answers

Is CVE-2022-41883 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2022-41883 being exploited in the wild.

How severe is CVE-2022-41883?

Low severity, with a CVSS score of 3.1, published 13 July 2026.

Which products and versions are affected?

tensorflow (PyPI) ECOSYSTEM:introduced=2.10.0,fixed=2.10.1; tensorflow-cpu (PyPI) ECOSYSTEM:introduced=2.10.0,fixed=2.10.1; tensorflow-gpu (PyPI) ECOSYSTEM:introduced=2.10.0,fixed=2.10.1.

Is there a fix for CVE-2022-41883?

Yes. tensorflow (PyPI): upgrade to 2.10.1 or later; tensorflow-cpu (PyPI): upgrade to 2.10.1 or later; tensorflow-gpu (PyPI): upgrade to 2.10.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2022-41883?

Check whether you run tensorflow (PyPI), tensorflow-cpu (PyPI) or tensorflow-gpu (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

• tensorflow (PyPI): upgrade to 2.10.1 or later

  pip install "tensorflow>=2.10.1"

• tensorflow-cpu (PyPI): upgrade to 2.10.1 or later

  pip install "tensorflow-cpu>=2.10.1"

• tensorflow-gpu (PyPI): upgrade to 2.10.1 or later

  pip install "tensorflow-gpu>=2.10.1"

Affected products

• tensorflow (PyPI) ECOSYSTEM:introduced=2.10.0,fixed=2.10.1
• tensorflow-cpu (PyPI) ECOSYSTEM:introduced=2.10.0,fixed=2.10.1
• tensorflow-gpu (PyPI) ECOSYSTEM:introduced=2.10.0,fixed=2.10.1

Identifiers

• CVE-2022-41883
• GHSA-w58w-79xv-6vcj
• PYSEC-2026-1042
• PYSEC-2026-3251
• PYSEC-2026-3376