CVE-2020-26267

Lack of validation in data format attributes in TensorFlow

HIGH

7.8

CVSS Score

Published: December 10, 2020 at 10:10 PM UTC

Updated: June 17, 2026 at 03:07 AM UTC

2 products affected across 2 vendorsTensorflowTensorFlow

Using tensorflow by tensorflow?

Get instant alerts when new vulnerabilities affect tensorflow - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.8

Exploit prediction

EPSS 0.2%

Description

In affected versions of TensorFlow the tf.raw_ops.DataFormatVecPermute API does not validate the src_format and dst_format attributes. The code assumes that these two arguments define a permutation of NHWC. This can result in uninitialized memory accesses, read outside of bounds and even crashes. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Tensorflow · Google

95%

v < 1.15.52.0.0 ≤ v < 2.0.42.1.0 ≤ v < 2.1.32.2.0 ≤ v < 2.2.22.3.0 ≤ v < 2.3.2

Affected range stops below 1.15.5, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.0.4, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.1.3, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.2.2, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.3.2, so it looks safe — our inference, not a vendor statement

TensorFlow · Tensorflow

60%

v < 1.15.5v < 2.0.4v < 2.1.3v < 2.2.2v < 2.3.2

Affected range stops below 1.15.5, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.0.4, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.1.3, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.2.2, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.3.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (2)

x_refsource_MISCPatchThird Party Advisory

Source: [email protected]

https://github.com/tensorflow/tensorflow/commit/ebc70b7a592420d3d2f359e4b1694c236b82c7ae

x_refsource_CONFIRMExploitPatchThird Party Advisory

Source: [email protected]

https://github.com/tensorflow/tensorflow/security/advisories/GHSA-c9f3-9wfr-wgh7

CVSS

7.8HIGH[email protected]

Attack Vector: LOCAL
Complexity: LOW
Privileges: LOW
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: HIGH
Integrity: HIGH
Availability: HIGH

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-125

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card