Improper Restriction of Operations within the Bounds of a Memory Buffer in Google TensorFlow

published 2019-04-23 7y ago modified 2026-06-17 4mo ago also GHSA-frxx-2m33-6wcr , PYSEC-2019-208 , PYSEC-2019-226 , PYSEC-2019-233 , EUVD-2019-0141

cvss: 8.8; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.8%; EPSS 0.8% chance of exploitation in 30 days, percentile 55%
public exploits: 0; none known

Google TensorFlow 1.7 and below is affected by: Buffer Overflow. The impact is: execute arbitrary code (local).

Patch / fix

fixed in 3 links 3

pypi tensorflow 1.7.1
pypi tensorflow-gpu 1.7.1
pypi tensorflow-cpu 1.7.1

Is CVE-2018-8825 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.75% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	8.8	CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD	2.0	6.8	AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub	3.0	8.8	CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
pypi	tensorflow	>=1.5.0, <1.7.1 <1.7.1	1.7.1
pypi	tensorflow-gpu	>=1.5.0, <1.7.1 <1.7.1	1.7.1
pypi	tensorflow-cpu	<1.7.1	1.7.1

Classification

Weakness

CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.