CVE-2022-41884Network attack vector

Denial of service via unchecked shape allocation

Published Nov 18, 2022 · Updated Apr 22, 2025

Denial-of-service flaw in ndarray_tensor_bridge in Google TensorFlow before 2.8.4, 2.9.0 through 2.9.2, and 2.10.0 allows remote authenticated users to crash a service via crafted NumPy shapes. The bridge passes zero-length and oversized shape dimensions to NumPy allocation without checking for a null return, then dereferences the invalid result and segfaults. Exploitation requires an exposed TensorFlow-consuming service to process attacker-controlled shapes and user interaction; impact is a process or service interruption, with no confidentiality or integrity effect reported.

CVSS severity4.8
Medium
EPSS probability0.34%
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

Denial-of-service flaw in ndarray_tensor_bridge in Google TensorFlow before 2.8.4, 2.9.0 through 2.9.2, and 2.10.0 allows remote authenticated users to crash a service via crafted NumPy shapes. The bridge passes zero-length and oversized shape dimensions to NumPy allocation without checking for a null return, then dereferences the invalid result and segfaults. Exploitation requires an exposed TensorFlow-consuming service to process attacker-controlled shapes and user interaction; impact is a process or service interruption, with no confidentiality or integrity effect reported.

The record

CVE
CVE-2022-41884
Published
Nov 18, 2022
Updated
Apr 22, 2025
Vendor
Google
Product
TensorFlow
Classifications
CWE-670, T1499
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Nov 18, 2022CVE publishedPublication date reported by the CVE source.
  2. Apr 22, 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.10.0, < 2.10.1
  2. Affected versionversion=< 2.8.4
  3. Affected versionversion=>= 2.9.0, < 2.9.3

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Google · TensorFlowversion=>= 2.10.0, < 2.10.1; version=< 2.8.4; version=>= 2.9.0, < 2.9.3

Published CVSS scores

4.8NVDCVSS:3.1/AV:N/AC:H/PR:L/UI:R/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
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-670Always-Incorrect Control Flow Implementation
T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

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