Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2020-26267: Lack of validation in data format attributes in TensorFlow

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: bazel-skylib1.0.3 (openSUSE:Leap 15.3) 1.0.3-bp153.2.1; bazel3.7 (openSUSE:Leap 15.3) 3.7.2-bp153.4.1; tensorflow2 (openSUSE:Leap 15.3) 2.6.0-bp153.2.3.1.
  • Severity is disputed: the assigning authority (CNA) scores it 4.4, NVD 7.8.

Low priority for now. Upgrade to bazel-skylib1.0.3 (openSUSE:Leap 15.3) 1.0.3-bp153.2.1; bazel3.7 (openSUSE:Leap 15.3) 3.7.2-bp153.4.1; tensorflow2 (openSUSE:Leap 15.3) 2.6.0-bp153.2.3.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Dec 10, 2020
Updated
Jun 16, 2026
EPSS
0.2% · 15th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CNA vs NVD score

NVD
7.8
CNA · GitHub_M
4.4
3.4 point gap

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2020-26267

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for google records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
googletensorflow

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • tensorflow tensorflow

    • < 1.15.5, >= 2.0.0, < 2.0.4, >= 2.1.0, < 2.1.3, >= 2.2.0, < 2.2.2, >= 2.3.0, < 2.3.2affected
Affected versions · NVD (5)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • google tensorflowbefore 1.15.5
  • google tensorflow2.0.0 and later · before 2.0.4
  • google tensorflow2.1.0 and later · before 2.1.3
  • google tensorflow2.2.0 and later · before 2.2.2
  • google tensorflow2.3.0 and later · before 2.3.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
openSUSE:Leap 15.3bazel-skylib1.0.3before 1.0.3-bp153.2.11.0.3-bp153.2.1
openSUSE:Leap 15.3bazel3.7before 3.7.2-bp153.4.13.7.2-bp153.4.1
openSUSE:Leap 15.3tensorflow2before 2.6.0-bp153.2.3.12.6.0-bp153.2.3.1
openSUSE:Leap 15.3tensorflow2_2_6_0-gnu-hpcbefore 2.6.0-bp153.2.3.12.6.0-bp153.2.3.1
openSUSE:Leap 15.3tensorflow2_2_6_0-gnu-openmpi2-hpcbefore 2.6.0-bp153.2.3.12.6.0-bp153.2.3.1
openSUSE:Leap 15.3tensorflow2-litebefore 2.6.0-bp153.2.3.12.6.0-bp153.2.3.1
PyPItensorflowfrom 2.0.0 · before 2.0.42.0.4
PyPItensorflowfrom 2.1.0 · before 2.1.32.1.3
PyPItensorflowfrom 2.2.0 · before 2.2.22.2.2
PyPItensorflowfrom 2.3.0 · before 2.3.22.3.2
PyPItensorflowbefore 1.15.51.15.5
PyPItensorflow-cpufrom 2.0.0 · before 2.0.42.0.4
PyPItensorflow-cpufrom 2.1.0 · before 2.1.32.1.3
PyPItensorflow-cpufrom 2.2.0 · before 2.2.22.2.2
PyPItensorflow-cpufrom 2.3.0 · before 2.3.22.3.2
PyPItensorflow-cpubefore 1.15.51.15.5
PyPItensorflow-gpufrom 2.0.0 · before 2.0.42.0.4
PyPItensorflow-gpufrom 2.1.0 · before 2.1.32.1.3
PyPItensorflow-gpufrom 2.2.0 · before 2.2.22.2.2
PyPItensorflow-gpufrom 2.3.0 · before 2.3.22.3.2
PyPItensorflow-gpubefore 1.15.51.15.5
SUSE:Package Hub 15 SP3bazel-skylib1.0.3before 1.0.3-bp153.2.11.0.3-bp153.2.1
SUSE:Package Hub 15 SP3bazel3.7before 3.7.2-bp153.4.13.7.2-bp153.4.1
SUSE:Package Hub 15 SP3tensorflow2before 2.6.0-bp153.2.3.12.6.0-bp153.2.3.1

+3

Same product

google: all records

Other highest-scoring records for the same primary product.

  • CVE-2023-25668TensorFlow vulnerable to heap out-of-buffer read in the QuantizeAndDequantize operation
    39Monitor
  • CVE-2023-25664TensorFlow vulnerable to Heap Buffer Overflow in AvgPoolGrad
    39Monitor
  • CVE-2022-41900FractionalMaxPool and FractionalAVGPool heap out-of-bounds acess in Tensorflow
    39Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2020-26271Dec 10, 2020 · Heap out of bounds access in MakeEdge in TensorFlow
    13Monitor
  • ← EarlierCVE-2020-26266Dec 10, 2020 · Uninitialized memory access in Eigen types in TensorFlow
    21Monitor
  • Later →CVE-2020-26268Dec 10, 2020 · Write to immutable memory region in TensorFlow
    17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
opensuse:bazel-skylib1.0.31.0.3-bp153.2.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:bazel3.73.7.2-bp153.4.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:tensorflow22.6.0-bp153.2.3.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:tensorflow2_2_6_0-gnu-hpc2.6.0-bp153.2.3.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:tensorflow2_2_6_0-gnu-openmpi2-hpc2.6.0-bp153.2.3.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:tensorflow2-lite2.6.0-bp153.2.3.1 · openSUSE:Leap 15.3Package registry (OSV)
PyPI:tensorflow1.15.5Package registry (OSV)
PyPI:tensorflow2.0.4Package registry (OSV)
PyPI:tensorflow2.1.3Package registry (OSV)
PyPI:tensorflow2.2.2Package registry (OSV)
PyPI:tensorflow2.3.2Package registry (OSV)
PyPI:tensorflow-cpu1.15.5Package registry (OSV)
PyPI:tensorflow-cpu2.0.4Package registry (OSV)
PyPI:tensorflow-cpu2.1.3Package registry (OSV)
PyPI:tensorflow-cpu2.2.2Package registry (OSV)
PyPI:tensorflow-cpu2.3.2Package registry (OSV)
PyPI:tensorflow-gpu1.15.5Package registry (OSV)
PyPI:tensorflow-gpu2.0.4Package registry (OSV)
PyPI:tensorflow-gpu2.1.3Package registry (OSV)
PyPI:tensorflow-gpu2.2.2Package registry (OSV)
PyPI:tensorflow-gpu2.3.2Package registry (OSV)
suse:bazel-skylib1.0.31.0.3-bp153.2.1 · SUSE:Package Hub 15 SP3Package registry (OSV)
suse:bazel3.73.7.2-bp153.4.1 · SUSE:Package Hub 15 SP3Package registry (OSV)
suse:tensorflow22.6.0-bp153.2.3.1 · SUSE:Package Hub 15 SP3Package registry (OSV)
suse:tensorflow2_2_6_0-gnu-hpc2.6.0-bp153.2.3.1 · SUSE:Package Hub 15 SP3Package registry (OSV)
suse:tensorflow2_2_6_0-gnu-openmpi2-hpc2.6.0-bp153.2.3.1 · SUSE:Package Hub 15 SP3Package registry (OSV)
suse:tensorflow2-lite2.6.0-bp153.2.3.1 · SUSE:Package Hub 15 SP3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records