CVE-2018-10055

CVE-2018-10055 is a high-severity vulnerability in Google Tensorflow with a CVSS 3.x base score of 8.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-119.

Key facts

Description

Invalid memory access and/or a heap buffer overflow in the TensorFlow XLA compiler in Google TensorFlow before 1.7.1 could cause a crash or read from other parts of process memory via a crafted configuration file.

Frequently asked questions

What is CVE-2018-10055?
Invalid memory access and/or a heap buffer overflow in the TensorFlow XLA compiler in Google TensorFlow before 1.7.1 could cause a crash or read from other parts of process memory via a crafted configuration file.
How severe is CVE-2018-10055?
CVE-2018-10055 has a CVSS 3.x base score of 8.1, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity none, and availability high.
Is CVE-2018-10055 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (35th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2018-10055?
CVE-2018-10055 affects Google Tensorflow. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2018-10055?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2018-10055 published?
CVE-2018-10055 was published on 2019-04-24 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Google Tensorflow

All CVEs affecting Google Tensorflow →

Other CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) vulnerabilities

Browse all CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) vulnerabilities →