TensorFlow · weakness class
Memory Corruption
215 CVEs
Every dot is a CVE in what this vendor ships; the named ones are the most at risk.
Every one of the 215 is a mark on the map. Named now: 1 to 26, most at risk first.
- Integer truncation in Shard API usage
- Segfault and data corruption in tensorflow-lite
- Integer overflow in TFLite
- Null pointer dereference in Grappler's `IsConstant` in Tensorflow
- Data leak in Tensorflow
- Null-dereference in Tensorflow
- Heap buffer overflow in Tensorflow
- Segfault in Tensorflow
- Undefined behavior in Tensorflow
- Out of bounds write in Tensorflow
- Out of bounds access in tensorflow-lite
- Heap buffer overflow in Tensorflow
- Segfault in Tensorflow
- Data corruption in tensorflow-lite
- Segfault in Tensorflow
- Undefined behavior in Tensorflow
- Integer overflow in Tensorflow
- Out of bounds read in Tensorflow
- Segfault in Tensorflow
- Out of bounds read and write in Tensorflow
- Read and Write outside of bounds in TFLite
- TensorFlow vulnerable to heap out-of-buffer read in the QuantizeAndDequantize operation
- Memory corruption in Tensorflow
- Integer overflow in TFLite array creation
- Null pointer dereference in tensorflow-lite
- Null-dereference in Tensorflow
exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it
Zoom in on the map and the dots under the middle of it are named where they are.
Data as of 2026-11-15. CVE List through 2026-11-15 · EPSS of 2026-11-15 · CISA KEV checked 2026-11-15. Sources: the CVE List, CISA KEV, EPSS, NVD, nuclei templates and public bug bounty data.