MediumVulnerability

CVE-2020-26268: TensorFlow crash through tf.raw_ops.ImmutableConst on memory mapped files

Source: NVD(opens in a new tab)
Identifier: CVE-2020-26268
Published: December 10, 2020
Record updated: October 10, 2026

Affected: tensorflow < 1.15.5, fixed in 1.15.5, released January 6, 2021, 26 days after disclosure
tensorflow >= 2.0.0, < 2.0.4, fixed in 2.0.4, released January 6, 2021, 26 days after disclosure
tensorflow >= 2.1.0, < 2.1.3, fixed in 2.1.3, released January 6, 2021, 26 days after disclosure
and 12 more
Known exploitation: Not listed in the CISA Known Exploited Vulnerabilities catalog at the last check.
EPSS: 0.2%

Summary

In affected versions of TensorFlow, the tf.raw_ops.ImmutableConst operation returns a constant tensor backed by a memory mapped file that is assumed immutable. When the tensor type is not an integral type, the operation writes to that memory area and crashes the Python interpreter. Once the file holds enough bytes for the tensor, the snippet causes a segmentation fault, because the allocator does not override the virtual method needed to be marked as returning an opaque handle.

Mitigation

This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0.

Details

Scores and exploitation

CVSS score: 4.4(medium)
Patch available: Yes
EPSS: 0.2%Estimated probability that this CVE is exploited in the next 30 days, from the FIRST Exploit Prediction Scoring System. Read on November 4, 2026.

Weaknesses and techniques

Weakness (CWE): CWE-471

Affected

Packages: tensorflow@< 1.15.5 (fixed: 1.15.5)
tensorflow@>= 2.0.0, < 2.0.4 (fixed: 2.0.4)
tensorflow@>= 2.1.0, < 2.1.3 (fixed: 2.1.3)
tensorflow@>= 2.2.0, < 2.2.2 (fixed: 2.2.2)
tensorflow@>= 2.3.0, < 2.3.2 (fixed: 2.3.2)
tensorflow-cpu@< 1.15.5 (fixed: 1.15.5)
tensorflow-cpu@>= 2.0.0, < 2.0.4 (fixed: 2.0.4)
tensorflow-cpu@>= 2.1.0, < 2.1.3 (fixed: 2.1.3)
tensorflow-cpu@>= 2.2.0, < 2.2.2 (fixed: 2.2.2)
tensorflow-cpu@>= 2.3.0, < 2.3.2 (fixed: 2.3.2)
tensorflow-gpu@< 1.15.5 (fixed: 1.15.5)
tensorflow-gpu@>= 2.0.0, < 2.0.4 (fixed: 2.0.4)
tensorflow-gpu@>= 2.1.0, < 2.1.3 (fixed: 2.1.3)
tensorflow-gpu@>= 2.2.0, < 2.2.2 (fixed: 2.2.2)
tensorflow-gpu@>= 2.3.0, < 2.3.2 (fixed: 2.3.2)
Vendors: Google

Classification

Attack type: Other
Attack sophistication: Moderate
AI component targeted: Framework
Impact: Integrity,
Availability
Labels: security

How this record was produced

Summaries, mitigations and labels on this page are generated automatically from the source. The linked source is authoritative. The source gives this advisory a description and no title, so the title above is a headline generated from the source text.

Original source: https://nvd.nist.gov/vuln/detail/CVE-2020-26268

First tracked: February 15, 2026 at 08:38 PM ET, from NVD/CVE Database

Classifier: claude-haiku-5-5, prompt v4

Classifier confidence: 95% (self-assessed)

Affected packages in the Exposure Registry

Matched by package name and ecosystem. Each entry shows whether the package delegates to a language model and how many tracked packages depend on it.

tensorflowPyPINo LLM dependency detected · 26 tracked dependents
tensorflow-gpuPyPINo LLM dependency detected · 2 tracked dependents

Summary

Mitigation

Affected packages in the Exposure Registry

Related items