cve.bz

CVE-2020-26270

3.3 lowEPSS 0.2%

Low (3.3) in google tensorflow. EPSS 0.2% chance of exploitation in the next 30 days. Fixed in tensorflow 1.15.5, 2.0.4, 2.1.3.

In affected versions of TensorFlow running an LSTM/GRU model where the LSTM/GRU layer receives an input with zero-length results in a CHECK failure when using the CUDA backend. This can result in a query-of-death vulnerability, via denial of service, if users can control the input to the layer. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0.

Severity

CVSS 3.1

3.3 low
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
EPSS
0.2% chance of exploitation in the next 30 days; higher than 6% of CVEs (scores of 2026-10-31)
CWE
CWE-20
Published
Modified
Record from
the NVD, synced

Affected

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-m648-33qf-v3gpPyPItensorflow<1.15.51.15.5
GHSA-m648-33qf-v3gpPyPItensorflow>=2.0.0 <2.0.42.0.4
GHSA-m648-33qf-v3gpPyPItensorflow>=2.1.0 <2.1.32.1.3
GHSA-m648-33qf-v3gpPyPItensorflow>=2.2.0 <2.2.22.2.2
GHSA-m648-33qf-v3gpPyPItensorflow>=2.3.0 <2.3.22.3.2
GHSA-m648-33qf-v3gpPyPItensorflow-cpu<1.15.51.15.5
GHSA-m648-33qf-v3gpPyPItensorflow-cpu>=2.0.0 <2.0.42.0.4
GHSA-m648-33qf-v3gpPyPItensorflow-cpu>=2.1.0 <2.1.32.1.3
GHSA-m648-33qf-v3gpPyPItensorflow-cpu>=2.2.0 <2.2.22.2.2
GHSA-m648-33qf-v3gpPyPItensorflow-cpu>=2.3.0 <2.3.22.3.2
GHSA-m648-33qf-v3gpPyPItensorflow-gpu<1.15.51.15.5
GHSA-m648-33qf-v3gpPyPItensorflow-gpu>=2.0.0 <2.0.42.0.4
GHSA-m648-33qf-v3gpPyPItensorflow-gpu>=2.1.0 <2.1.32.1.3
GHSA-m648-33qf-v3gpPyPItensorflow-gpu>=2.2.0 <2.2.22.2.2
GHSA-m648-33qf-v3gpPyPItensorflow-gpu>=2.3.0 <2.3.22.3.2
PYSEC-2020-256PyPItensorflow<1.15.5
>=2.0.0 <2.0.4
>=2.1.0 <2.1.3
>=2.2.0 <2.2.2
>=2.3.0 <2.3.2		1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2
PYSEC-2020-301PyPItensorflow-cpu<1.15.5
>=2.0.0 <2.0.4
>=2.1.0 <2.1.3
>=2.2.0 <2.2.2
>=2.3.0 <2.3.2		1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2
PYSEC-2020-336PyPItensorflow-gpu<1.15.5
>=2.0.0 <2.0.4
>=2.1.0 <2.1.3
>=2.2.0 <2.2.2
>=2.3.0 <2.3.2		1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2

References

Check your stackJSON