CVE-2020-26268

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine with a low-privilege account. Limited direct impact.

Exploit odds

0.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2020-12-10 23:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 03:07 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.2% in the next 30 days (EPSS).
• Severity: 4.4 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2020-12-10 23:15 UTC

Last modified

2026-06-17 03:07 UTC

Exploit probability

0.2% · EPSS, next 30 days

Weakness

CWE-471

Record status

Modified

Affected

• Google Tensorflow < 1.15.5
• Google Tensorflow < 2.0.4
• Google Tensorflow < 2.1.3
• Google Tensorflow < 2.2.2
• Google Tensorflow < 2.3.2

Attack profile CVSS 3.1 · 4.4

Attack vector

Local

Complexity

Low

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

Low

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2020-26268.md and follow it. Check whether this project is affected by CVE-2020-26268. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge