How severe is CVE-2022-35937?

CVE-2022-35937 has a CVSS score of 7/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-35937?

CVE-2022-35937 affects the following packages: tensorflow (PyPI), tensorflow (PyPI), tensorflow (PyPI), tensorflow-cpu (PyPI), tensorflow-cpu (PyPI), tensorflow-cpu (PyPI), tensorflow-gpu (PyPI), tensorflow-gpu (PyPI), and 1 more. Ecosystems affected: PyPI.

How do I fix CVE-2022-35937?

Update tensorflow to 2.7.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-35937 is resolved across your whole dependency graph.

How do I detect CVE-2022-35937 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tensorflow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-35937 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is CVE-2022-35937 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-35937 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-35937?

CVE-2022-35937 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 47th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-35937?

CVE-2022-35937 is classified as Out-of-bounds Read (CWE-125). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-35937 published, and has it been updated?

CVE-2022-35937 was published on September 16, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

HIGH severity

CVE-2022-35937 — tensorflow

HIGHFix: tensorflow/tensorflow@595a65a

CVE-2022-35937 is a high-severity (CVSS 7) Out-of-bounds Read vulnerability in tensorflow. A fix is available for tensorflow — see the affected versions and patch details below.

OOB read in `Gather_nd` op in TensorFlow Lite

Also known asBIT-tensorflow-2022-35937GHSA-pxrw-j2fv-hx3hPYSEC-2026-1027PYSEC-2026-3226PYSEC-2026-3359

Published

Sep 16, 2022

Updated

Oct 28, 2026

Affected

9 pkgs

Patched

9 / 9

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-35937.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs47th percentile — riskier than 47% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

9 pkgs affected

🐍tensorflow🐍tensorflow🐍tensorflow🐍tensorflow-cpu🐍tensorflow-cpu🐍tensorflow-cpu🐍tensorflow-gpu🐍tensorflow-gpu+1 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

The GatherNd function takes arguments that determine the sizes of inputs and outputs. If the inputs given are greater than or equal to the sizes of the outputs, an out-of-bounds memory read is triggered.

Patches

We have patched the issue in GitHub commit 595a65a3e224a0362d7e68c2213acfc2b499a196.

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.

For more information

Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.

Attribution

This vulnerability has been reported by Hui Peng from Baidu Security.

Affected Packages

9 total 9 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`tensorflow`	all versions	2.7.2`pip install --upgrade 'tensorflow==2.7.2'`
🐍PyPI	`tensorflow`	≥ 2.8.0&&< 2.8.1	2.8.1`pip install --upgrade 'tensorflow==2.8.1'`
🐍PyPI	`tensorflow`	≥ 2.9.0&&< 2.9.1	2.9.1`pip install --upgrade 'tensorflow==2.9.1'`
🐍PyPI	`tensorflow-cpu`	all versions	2.7.2`pip install --upgrade 'tensorflow-cpu==2.7.2'`
🐍PyPI	`tensorflow-cpu`	≥ 2.8.0&&< 2.8.1	2.8.1`pip install --upgrade 'tensorflow-cpu==2.8.1'`
🐍PyPI	`tensorflow-cpu`	≥ 2.9.0&&< 2.9.1	2.9.1`pip install --upgrade 'tensorflow-cpu==2.9.1'`

Affected Products

1 product · 7 configurations

Application

tensorflowgoogle

≥ 2.9.0 && < 2.9.1

1 version

2.10

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tensorflow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update tensorflow to 2.7.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-35937 is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

### Impact The [`GatherNd`](https://github.com/tensorflow/tensorflow/blob/f463040eb3997e42e60a2ffc6dc72de7ef11dbb4/tensorflow/lite/kernels/gather_nd.cc#L105-L111) function takes arguments that determine the sizes of inputs and outputs. If the inputs given are greater than or equal to the sizes of the outputs, an out-of-bounds memory read is triggered. ### Patches We have patched the issue in GitHub commit [595a65a3e224a0362d7e68c2213acfc2b499a196](https://github.com/tensorflow/tensorflow/commit/595a65a3e224a0362d7e68c2213acfc2b499a196). The fix will be included in TensorFlow 2.10.0. We will

O3 Security · Impact-Aware SCA

Is CVE-2022-35937 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

High

Raw vector

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

CWE Classification

CWE-125Out-of-bounds Read

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

tensorflow

7.9/10

Code-Review7/10

Maintained10/10

Dependency-Update-Tool10/10

Branch-ProtectionN/A

Vulnerabilities0/10

Assessed Nov 9, 2026

Timeline

Disclosed

Sep 16, 2022

Last updated

Oct 28, 2026

Identifiers

CVE-2022-35937

GHSA-pxrw-j2fv-hx3h

BIT-tensorflow-2022-35937

PYSEC-2026-1027

PYSEC-2026-3226

References

Advisorygithub.com · CVE 2022 35937.json Advisorygithub.com · GHSA pxrw j2fv hx3h Advisorynvd.nist.gov · CVE 2022 35937 Fixgithub.com · 595a65a3e224a0362d7e68c2213acfc2b499a196 Webgithub.com · gather nd.cc Webgithub.com · v2.10.0 Packagegithub.com · tensorflow

Related vulnerabilities

This CVE is high severity; 7 of 8 other CVEs affecting tensorflow are rated as high or higher (top: high).

CVE-2023-33976CVE-2023-25661CVE-2023-25670CVE-2023-25665CVE-2023-27579CVE-2023-25673CVE-2023-25663CVE-2023-25658

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026