CVE-2020-26270

creationtimestamp| type| source ---|---|--- 2020-12-11 02:34:37+00:00| seen| https://t.me/cibsecurity/19642 2020-12-11 02:37:43+00:00| seen| https://t.me/cibsecurity/19662 2020-12-11 03:25:32+00:00| seen| https://t.me/cibsecurity/19682 2020-12-11 04:25:26+00:00| seen| https://t.me/cibsecurity/197...

aglvq (=1.0.0), beacon-trellis (=0.1.0) +64 more potentially affected by CVE-2020-26270 via tensorflow (>=2.1.0 <=2.1.2)

tensorflow PYPI version =2.1.0, =3.0.0, =0.0.1, =0.2.0, =0.0.2, =0.1.0, =1.1.0, =0.2.0rc1, =0.2.0rc3 and more Source cves: CVE-2020-26270 Source advisory: OSV:PYSEC-2020-256...

accuinsight (>=1.0.47 <=1.0.61), alphad3m (>=0.10.0 <=0.10.0.dev1) +86 more potentially affected by CVE-2020-26270 via tensorflow (>=2.2.0 <=2.2.1)

tensorflow PYPI version =2.2.0, =1.0.47, =0.10.0, =0.5.0, =0.2.0, =0.0.6, =1.2.0, =1.0.0, =0.0.15, =0.0.16 and more Source cves: CVE-2020-26270 Source advisory: OSV:GHSA-M648-33QF-V3GP...

tensorflowjs (>=1.5.2 <=1.7.4) potentially affected by CVE-2020-26270 via tensorflow-cpu (=2.1.0)

tensorflow-cpu PYPI version =2.1.0 is affected by a known vulnerability. The following packages have a transitive dependency on tensorflow-cpu and may be impacted: - tensorflowjs =1.5.2, =1.7.4 Source cves: CVE-2020-26270 Source advisory: OSV:GHSA-M648-33QF-V3GP...