CVE-2022-23578Network attack vector

Memory exhaustion via unreleased invalid-node kernel

Published Feb 4, 2022 · Updated Apr 22, 2025

Memory leak in Google TensorFlow before 2.5.3, 2.6.0 through 2.6.2, and 2.7.0 allows remote authenticated users to exhaust memory. In ImmutableExecutorState::Initialize, a failed create_kernel call can leave an allocated OpKernel in item->kernel, which the error path overwrites with nullptr without calling delete_kernel. An authenticated network path that submits invalid graph nodes is required; repeated triggers consume process memory and can interrupt the hosting service without reported data access or modification.

CVSS severity4.3
Medium
EPSS probability0.72%
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

Memory leak in Google TensorFlow before 2.5.3, 2.6.0 through 2.6.2, and 2.7.0 allows remote authenticated users to exhaust memory. In ImmutableExecutorState::Initialize, a failed create_kernel call can leave an allocated OpKernel in item->kernel, which the error path overwrites with nullptr without calling delete_kernel. An authenticated network path that submits invalid graph nodes is required; repeated triggers consume process memory and can interrupt the hosting service without reported data access or modification.

The record

CVE
CVE-2022-23578
Published
Feb 4, 2022
Updated
Apr 22, 2025
Vendor
Google
Product
TensorFlow
Classifications
CWE-401, T1499.004
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Feb 4, 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.5.3
  2. Affected versionversion=>= 2.6.0, < 2.6.3
  3. Affected versionversion=>= 2.7.0, < 2.7.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Google · TensorFlowversion=< 2.5.3; version=>= 2.6.0, < 2.6.3; version=>= 2.7.0, < 2.7.1

Published CVSS scores

4.3NISTCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
4.0NISTAV:N/AC:L/Au:S/C:N/I:N/A:P

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-401Missing Release of Memory after Effective Lifetime
T1499.004Endpoint Denial of Service: Application or System Exploitation

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