Skip to content
Noroxi
CVE-2022-36016· NVD / CVE Program· CNA GitHub_M

`CHECK`-fail in `tensorflow::full_type::SubstituteFromAttrs` in TensorFlow

TensorFlow is an open source platform for machine learning. When `tensorflow::full_type::SubstituteFromAttrs` receives a `FullTypeDef& t` that is not exactly three args, it triggers a `CHECK`-fail instead of returning a status. We have patched the issue in GitHub commit 6104f0d4091c260ce9352f9155f7e9b725eab012. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Sep 16, 2022
Updated
Jun 17, 2026
EPSS
0.7% · 51th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.7%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.5
CNA · GitHub_M
5.9
1.6 point gap

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

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

Affected systems

VendorProduct
googletensorflow

Affected versions

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

  • google tensorflowbefore 2.7.2
  • google tensorflow2.8.0 and later · before 2.8.1
  • google tensorflow2.9.0 and later · before 2.9.1
  • google tensorflow2.10

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

    • < 2.7.2, >= 2.8.0, < 2.8.1, >= 2.9.0, < 2.9.1affected

Package-level exposure

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

EcosystemPackageAffected rangeFix
PyPItensorflowfrom 2.8.0 · before 2.8.12.8.1
PyPItensorflowfrom 2.9.0 · before 2.9.12.9.1
PyPItensorflowbefore 2.7.22.7.2
PyPItensorflow-cpufrom 2.8.0 · before 2.8.12.8.1
PyPItensorflow-cpufrom 2.9.0 · before 2.9.12.9.1
PyPItensorflow-cpubefore 2.7.22.7.2
PyPItensorflow-gpufrom 2.8.0 · before 2.8.12.8.1
PyPItensorflow-gpufrom 2.9.0 · before 2.9.12.9.1
PyPItensorflow-gpubefore 2.7.22.7.2

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
  • CVE-2022-35939Out of bounds write in `scatter_nd` op in TensorFlow Lite
    39Monitor
  • CVE-2022-23587Integer overflow in Tensorflow
    39Monitor
  • CVE-2020-15208Data corruption in tensorflow-lite
    39Monitor

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
PyPI:tensorflow2.7.2Package registry (OSV)
PyPI:tensorflow2.8.1Package registry (OSV)
PyPI:tensorflow2.9.1Package registry (OSV)
PyPI:tensorflow-cpu2.7.2Package registry (OSV)
PyPI:tensorflow-cpu2.8.1Package registry (OSV)
PyPI:tensorflow-cpu2.9.1Package registry (OSV)
PyPI:tensorflow-gpu2.7.2Package registry (OSV)
PyPI:tensorflow-gpu2.8.1Package registry (OSV)
PyPI:tensorflow-gpu2.9.1Package 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

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

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-617 · Reachable Assertion

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

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

All records