CVE-2019-16778

What it is

In TensorFlow before 1.15, a heap buffer overflow in UnsortedSegmentSum can be produced when the Index template argument is int32. In this case data_size and num_segments fields are truncated from int64 to int32 and can produce negative numbers, resulting in accessing out of bounds heap memory. This is unlikely to be exploitable and was detected and fixed internally in TensorFlow 1.15 and 2.0.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account, but needs a user to act. Limited direct impact.

Exploit odds

0.8% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2019-12-16 21:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 02:22 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.8% in the next 30 days (EPSS).
• Severity: 2.6 LOW (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2019-12-16 21:15 UTC

Last modified

2026-06-17 02:22 UTC

Exploit probability

0.8% · EPSS, next 30 days

Weakness

CWE-122

Record status

Modified

Affected

• Google Tensorflow < 1.15.0

Attack profile CVSS 3.1 · 2.6

Attack vector

Network

Complexity

High

Privileges needed

Low

User interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

Low

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2019-16778.md and follow it. Check whether this project is affected by CVE-2019-16778. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge