CVE-2022-36017 | Segfault in `Requantize` in TensorFlow

TensorFlow is an open source platform for machine learning. If `Requantize` is given `input_min`, `input_max`, `requested_output_min`, `requested_output_max` tensors of a nonzero rank, it results in a segfault that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 785d67a78a1d533759fcd2f5e8d6ef778de849e0. 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.

Published: 2022-09-16 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-36017 is rated Low Risk (35.1/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.40%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-36017

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.13% 0.40% +0.28%
2 2025-09-18 0.16% 0.13% -0.03%
3 2025-04-09 — 0.16% —

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-36017

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.9 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.2 3.6 [email protected]
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2022-36017

GitHub Security Advisory for CVE-2022-36017

GHSA-wqmc-pm8c-2jhc · Severity: medium · Ecosystem: pip — TensorFlow vulnerable to segfault in `Requantize`

OS Trackers for CVE-2022-36017

vendor priority summary link
debian unimportant CVE-2022-36017 unimportant priority: Debian including 1 source packages (tensorflow), 2 status rows across 2 suites (forky, sid): resolved 2. https://security-tracker.debian.org/tracker/CVE-2022-36017

Affected software / configurations for CVE-2022-36017

Vendor Product Version Raw CPE
google tensorflow < 2.7.2 cpe:2.3:a:google:tensorflow:*:*:*:*:*:*:*:*
google tensorflow >= 2.8.0, < 2.8.1 cpe:2.3:a:google:tensorflow:*:*:*:*:*:*:*:*
google tensorflow >= 2.9.0, < 2.9.1 cpe:2.3:a:google:tensorflow:*:*:*:*:*:*:*:*
google tensorflow 2.10 cpe:2.3:a:google:tensorflow:2.10:rc0:*:*:*:*:*:*
google tensorflow 2.10 cpe:2.3:a:google:tensorflow:2.10:rc1:*:*:*:*:*:*
google tensorflow 2.10 cpe:2.3:a:google:tensorflow:2.10:rc2:*:*:*:*:*:*
google tensorflow 2.10 cpe:2.3:a:google:tensorflow:2.10:rc3:*:*:*:*:*:*

References for CVE-2022-36017

cvelogic Threat Intelligence