CVE-2022-36014· NVD / CVE Program· CNA GitHub_M

Null-dereference in `mlir::tfg::TFOp::nameAttr` in TensorFlow

Noroxi assessment

Priority: Monitor (action score 30/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.71% (FIRST EPSS); higher than 52.4% of all records.
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.
Fixed version: tensorflow (PyPI) 2.8.1, 2.9.1, 2.7.2; tensorflow-cpu (PyPI) 2.8.1, 2.9.1, 2.7.2; tensorflow-gpu (PyPI) 2.8.1, 2.9.1, 2.7.2.

Low priority for now. Upgrade to tensorflow (PyPI) 2.8.1, 2.9.1, 2.7.2; tensorflow-cpu (PyPI) 2.8.1, 2.9.1, 2.7.2; tensorflow-gpu (PyPI) 2.8.1, 2.9.1, 2.7.2 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

TensorFlow is an open source platform for machine learning. When `mlir::tfg::TFOp::nameAttr` receives null type list attributes, it crashes. We have patched the issue in GitHub commits 3a754740d5414e362512ee981eefba41561a63a6 and a0f0b9a21c9270930457095092f558fbad4c03e5. 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% · 52th percentile
CWE: CWE-476

Report tools

JSON

Action score

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.

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.

Running WordPress? Scan your site free with WP Lens

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.

Vendor	Product	CPE
google	tensorflow	cpe:2.3:a:google:tensorflow

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.

Ecosystem	Package	Affected range	Fix
PyPI	tensorflow	from 2.8.0 · before 2.8.1	2.8.1
PyPI	tensorflow	from 2.9.0 · before 2.9.1	2.9.1
PyPI	tensorflow	before 2.7.2	2.7.2
PyPI	tensorflow-cpu	from 2.8.0 · before 2.8.1	2.8.1
PyPI	tensorflow-cpu	from 2.9.0 · before 2.9.1	2.9.1
PyPI	tensorflow-cpu	before 2.7.2	2.7.2
PyPI	tensorflow-gpu	from 2.8.0 · before 2.8.1	2.8.1
PyPI	tensorflow-gpu	from 2.9.0 · before 2.9.1	2.9.1
PyPI	tensorflow-gpu	before 2.7.2	2.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 / package	Fixed version	Source
PyPI:tensorflow	2.7.2	Package registry (OSV)
PyPI:tensorflow	2.8.1	Package registry (OSV)
PyPI:tensorflow	2.9.1	Package registry (OSV)
PyPI:tensorflow-cpu	2.7.2	Package registry (OSV)
PyPI:tensorflow-cpu	2.8.1	Package registry (OSV)
PyPI:tensorflow-cpu	2.9.1	Package registry (OSV)
PyPI:tensorflow-gpu	2.7.2	Package registry (OSV)
PyPI:tensorflow-gpu	2.8.1	Package registry (OSV)
PyPI:tensorflow-gpu	2.9.1	Package 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-476 · NULL Pointer Dereference

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.

Change log

Fix✗ → ✓Sep 28, 2026, 10:44 PM UTC

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

References

github.com/tensorflow/tensorflow/blob/master/tensorflow/core/ir/importexport/graphdef_import.cc

Show all references (3 more)

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

All records