CVE-2022-35987Public exploitNetwork attack vector

Process crash via mismatched DenseBincount weights

Published Sep 16, 2022 · Updated Apr 23, 2025

Reachable assertion in affected Google TensorFlow releases allows remote attackers to crash a hosting process through malformed tensors. DenseBincount accepts a weights tensor whose shape neither matches the input nor contains zero elements, allowing downstream code to reach a fatal CHECK instead of rejecting the argument. Affected versions are before 2.7.2, 2.8.0, and 2.9.0; attacker-controlled tensors must reach the operation, and the failure terminates the hosting process without disclosing or altering data.

CVSS severity7.5
High
EPSS probability0.48%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Reachable assertion in affected Google TensorFlow releases allows remote attackers to crash a hosting process through malformed tensors. DenseBincount accepts a weights tensor whose shape neither matches the input nor contains zero elements, allowing downstream code to reach a fatal CHECK instead of rejecting the argument. Affected versions are before 2.7.2, 2.8.0, and 2.9.0; attacker-controlled tensors must reach the operation, and the failure terminates the hosting process without disclosing or altering data.

The record

CVE
CVE-2022-35987
Published
Sep 16, 2022
Updated
Apr 23, 2025
Vendor
Google
Product
TensorFlow
Classifications
CWE-617, T1499.004
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Sep 16, 2022CVE publishedPublication date reported by the CVE source.
  2. Apr 23, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 2.7.2
  2. Affected versionversion=>= 2.8.0, < 2.8.1
  3. Affected versionversion=>= 2.9.0, < 2.9.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Google · TensorFlowversion=< 2.7.2; version=>= 2.8.0, < 2.8.1; version=>= 2.9.0, < 2.9.1

Published CVSS scores

7.5NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-617Reachable Assertion
T1499.004Application or System Exploitation

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo